INTER-2266: Improve move tag workflow#168
Conversation
Replace hardcoded tag move with a workflow that accepts a target tag. It also fixes git user identity. Related-Task: INTER-2266
|
There was a problem hiding this comment.
Pull request overview
This PR updates the GitHub Actions workflow used to move a major-version tag (e.g., v1) so it can be moved to an arbitrary existing target tag, with added validation and updated git identity configuration.
Changes:
- Parameterize the workflow to accept
targetandmajor_versioninputs (instead of hardcodingv1). - Add checks that the target exists as a tag and is reachable from
main. - Simplify tag update/push steps and set the git user identity for the workflow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Replace grep-based branch check with git merge-base --is-ancestor. Related-Task: INTER-2266
Use ^{} to dereference annotated tags
Related-Task: INTER-2266
Use refs/tags/ prefix in git rev-list. Related-Task: INTER-2266
mcnulty-fp
left a comment
There was a problem hiding this comment.
LGTM, thanks for working on this.
To clarify, the process now:
- PR is merged with changes to actions/workflows
- Manually push a tag like v1.x.y after merging
- Run this workflow with the new tag as the
targetinput
If that's correct, it'd be good to document that process in the readme.md. If not, could you add the expected process to the readme.md? :)
pnpm exec changesetto create a changeset. |
Summary
mainbranch