ci: allow manually triggering the develop-to-main sync - #103
Merged
Merged
Conversation
| concurrency: | ||
| group: sync-develop-to-main | ||
| # just in case previous run is stuck | ||
| cancel-in-progress: true |
Collaborator
There was a problem hiding this comment.
not sure if this is a good idea if we get a burst of commits incoming?
we can add a bool input "force_execute" with default false and then use
cancel-in-progress: ${{ inputs.force_execute }} so that manually we can cancel the queue
Contributor
Author
There was a problem hiding this comment.
since those fire pretty fast, I was thinking overlaps will rarely if not never happen, but I guess it can't hurt. made the change
HereThereBeDragons
approved these changes
Sep 11, 2026
![quartz-sync[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
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
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.
Motivation
The automatic
develop→mainsynchronization can occasionally become stuck because of GitHub Actions infrastructure issues and cannot be restarted in place.Allow maintainers to manually trigger a replacement synchronization run.
Fixes #89
Technical Details
workflow_dispatchtrigger tosync_develop_to_main.yml.cancel-in-progressfor the existing concurrency group so a new run supersedes a stuck or outdated synchronization.origin/developcommit instead of relying onGITHUB_SHA, which may refer to another branch when manually dispatched.develop.Submission Checklist