docs: rename post-release sync branch to tmp/sync-main/{tag}#402
Open
hdamker wants to merge 1 commit intocamaraproject:mainfrom
Open
docs: rename post-release sync branch to tmp/sync-main/{tag}#402hdamker wants to merge 1 commit intocamaraproject:mainfrom
hdamker wants to merge 1 commit intocamaraproject:mainfrom
Conversation
Aligns with tooling#98 — the tmp/ prefix signals the branch is
temporary, sync-main/ describes its purpose, avoiding confusion
with the permanent pre-release/{tag} pointer branch.
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
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.
What type of PR is this?
Documentation update
What this PR does / why we need it:
Updates the detailed design document to reflect the renamed post-release sync branch from
post-release/rX.Ytotmp/sync-main/rX.Y. Thetmp/prefix signals the branch is temporary (deleted after PR merge), andsync-main/describes its purpose — avoiding confusion with the permanentpre-release/rX.Ypointer branch.Which issue(s) this PR fixes:
Related: camaraproject/tooling#98 (implementation change)
Special notes for reviewers:
Two occurrences in Section 8 (Post-Release Automation) of
CAMARA-Release-Creation-Detailed-Design.md:All other "post-release" references in the doc are descriptive text (e.g., "post-release sync PR", "Post-Release Automation") and remain unchanged.
Changelog input
Additional documentation