Fix workflow job order to prevent duplicate runs#118
Merged
Conversation
This reverts commit ae2abb8.
Move prepare_release_pr job to run after create_release_pr to prevent duplicate workflow executions. Update dependency chain and commit message for clarity.
marians
approved these changes
Feb 5, 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 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.
Summary
create-release-prworkflow to prevent duplicate workflow executionsprepare_release_prjob to run aftercreate_release_prinstead of beforeProblem
The previous job order caused the workflow to trigger duplicate runs when the
prepare_release_prjob pushed changes to the release branch.Solution
By creating the PR first and then running the preparation job, the workflow avoids triggering itself again. The preparation job now runs as a follow-up step after the PR is already created.