ci: skip test jobs on tags (tags only publish)#222
Merged
Conversation
All six test jobs (version_tables_in_sync + bridge_example_*) now carry `if: !startsWith(github.ref, 'refs/tags/')`, so a tag push runs only the publish job. publish `needs:` those jobs, so its `if` gains `!cancelled()` to run despite the skipped needs (it still gates on the tag ref). Tests run on branches/PRs before a release tag is cut.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
On a tag push, the CI now runs only the
publishjob — the test jobs no longer re-run on release tags.Why
The bridge example test jobs (macOS/iOS/Android/Windows/Linux) and the version-tables check already run on branch/PR pushes before a release tag is cut. Re-running the heavy device/emulator suites on the tag is redundant and can flake, delaying/blocking a publish.
How
version_tables_in_sync+bridge_example_*) gainsif: ${{ !startsWith(github.ref, 'refs/tags/') }}, so they're skipped on tag pushes.publishneeds:thebridge_example_*jobs; a skipped dependency would normally cascade-skip it, so itsifgains a!cancelled()status function:if: ${{ !cancelled() && startsWith(github.ref, 'refs/tags/v') }}. It still only runs onv*tags, now regardless of the skipped needs.Branch/PR behavior is unchanged (publish's tag guard keeps it off non-tags; tests run as before).