ci: don't cancel in-progress linear release runs on main#23766
Merged
Conversation
matifali
reviewed
Mar 30, 2026
dc6f783 to
51f92e6
Compare
matifali
reviewed
Mar 30, 2026
Comment on lines
+16
to
+17
| # Queue rather than cancel so back-to-back pushes to main don't cancel the first sync. | ||
| cancel-in-progress: false |
Member
There was a problem hiding this comment.
How Linear Sync works is that it syncs all commits between the last sync and the current commit. So technically it doesn't have to run on each commit to main.
With cancel-in-progress: true, we were saving for some CI minutes.
Another option is to move this to run on schedule, but that has the downside of making Sync stale.
Member
There was a problem hiding this comment.
Non-blocking from me. As the cost is not a big issue here. I wanted to note the point. Thanks
Member
Author
There was a problem hiding this comment.
We're saving max like 30 seconds of CI by cancelling, so I figured it was fine. We don't have any other jobs that regularly cause red Xs that we don't try and do something about.
matifali
approved these changes
Mar 30, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The Linear Release workflow had
cancel-in-progress: trueunconditionally, so a new push tomainwould cancel an already-running sync. This meant successive PR merges would show you a bunch of red Xs on CI, even though nothing was wrong.Other workflows like CI guard against this with
cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}.This PR does the same thing to the linear release workflow. The job will be queued instead.
Letting the job finish is not particularly wasteful or anything since the sync takes 30~ seconds in CI time.