feat(skills): add ama-logs-tag-release skill#1706
Open
zanejohnson-azure wants to merge 2 commits into
Open
Conversation
Documents how to create and push the release tag (e.g. 3.4.0) on the merge commit of the release-notes PR, following the lightweight-tag convention used by 3.3.0 and 3.4.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The documented manual procedure uses `git tag -a` (annotated) and follows up with a GitHub Release draft using auto-generated notes against the previous prod tag. The earlier version of this skill incorrectly defaulted to lightweight tags and stopped after pushing the tag. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Adds
.github/skills/ama-logs-tag-release/SKILL.mddocumenting how to create and push the release git tag (e.g.3.4.0) on the merge commit of the release-notes PR.Mirrors the lightweight-tag convention used by
3.3.0and3.4.0. Companion to theama-logs-update-charts-release-notesskill — that one ships the PR; this one tags it after merge.Covers:
ci_prodorigin/ci_prodrefs/tags/<VERSION>(never--tags)vprefix, never force-push existing release tags, never tag from an un-merged PRSkill file only — no production code changes.