-
Notifications
You must be signed in to change notification settings - Fork 127
Unified CI workflow #618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unified CI workflow #618
Conversation
- Create single workflow for building, testing, linting, and doc generation - Update publish docs workflow to use pre-built docs - Create empty documentation catalog
it seems like you haven't added any nanpa changeset files to this PR. if this pull request includes changes to code, make sure to add a changeset, by writing a file to
refer to the manpage for more information. |
cancel-in-progress: true | ||
|
||
env: | ||
TESTS: "FunctionTests SDKTests RoomTests PublishDataTests PublishBufferCapturerTests VideoViewTests TrackTests" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this really necessary? seems like an easy trap that we'll add new tests but forget to add them here and thus CI won't actually run them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part was copied from the existing test workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes Ben is right, but some tests don't run on CI/Simulator needs device etc. We can organize this in another PR.
When run for PRs, ref name can contain "/" which is not file path safe.
This PR creates a unified CI workflow that performs building, testing, linting, and documentation generation. This brings several advantages:
symbol-graph
set to true will trigger a release build with symbol graphs emitted—these will then be used to build docs.