| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This reduces the likelihood of publishing a tag but not a release.
There was a problem hiding this comment.
This PR reorders workflow steps to create the mergeback PR after the GitHub release is created, reducing the likelihood of publishing a tag but not a release.
Sorry, something went wrong.
| --notes-file "$PARTIAL_CHANGELOG" | ||
|
|
||
| - name: Create mergeback branch and PR | ||
| if: ${{ endsWith(github.ref_name, steps.getVersion.outputs.latest_release_branch) }} |
There was a problem hiding this comment.
I also changed this so that we will try to open the mergeback even if the tag exists. This means we can retry generating the mergeback if this workflow fails, even if the tag is already published.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This reduces the likelihood of publishing a tag but not a release.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Dev only
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Merge / deployment checklist