Skip to content

docs: rename post-release sync branch to tmp/sync-main/{tag}#402

Open
hdamker wants to merge 1 commit intocamaraproject:mainfrom
hdamker:fix/rename-sync-branch
Open

docs: rename post-release sync branch to tmp/sync-main/{tag}#402
hdamker wants to merge 1 commit intocamaraproject:mainfrom
hdamker:fix/rename-sync-branch

Conversation

@hdamker
Copy link
Collaborator

@hdamker hdamker commented Mar 1, 2026

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.Y to tmp/sync-main/rX.Y. The tmp/ prefix signals the branch is temporary (deleted after PR merge), and sync-main/ describes its purpose — avoiding confusion with the permanent pre-release/rX.Y pointer 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:

  • Section 8.3: Sync PR specification table (branch name)
  • Section 8.4: Branch cleanup table (branch lifecycle)

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

release-note
n/a

Additional documentation

docs
Updated CAMARA-Release-Creation-Detailed-Design.md Section 8.3 and 8.4

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant