Skip to content

feat(skill): publish-release flips GitHub default to main on first release #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
amcheste merged 2 commits into from
May 12, 2026
Merged

feat(skill): publish-release flips GitHub default to main on first release #84

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
80282ff
feat(skill): publish-release flips GitHub default to main on first re…
amcheste-ai-agent May 12, 2026
91886e0
Merge branch 'develop' into feat/publish-release-default-flip
amcheste May 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions claude-skills/publish-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,10 +92,32 @@ Show the user the release pipeline URL and confirm the tag was pushed. Let them
- If the version contains `-` (e.g. `-beta.1`, `-rc.1`) it is published as a **pre-release** and will not show as the latest version
- If it is a stable version (e.g. `1.0.0`) it becomes the **latest** release after all pipeline gates pass

## Step 5 — Ensure `main` is the GitHub default branch

`develop` is the integration trunk and stays the same. GitHub's "default branch" repo setting is separate — it controls landing page, `git clone` target, and PR-base UI default. The convention (see [Branching & Releases](https://github.com/amcheste/engineering-handbook/blob/develop/docs/workflows/branching-and-releases.md#github-default-branch-setting)) is:

- Pre-release: GitHub default = `develop` (the only meaningful state)
- Post-release: GitHub default = `main` (external visitors see the shipped product)

Run this unconditionally at the end of the release flow. It's idempotent: on the first release it flips develop → main, on every subsequent release it's a no-op.

```bash
current=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
if [ "$current" != "main" ]; then
gh repo edit --default-branch main
echo "GitHub default branch flipped to main (first release)."
else
echo "GitHub default branch already main."
fi
```

Contributors keep branching from and PR'ing to `develop` — only what GitHub renders on the repo landing page changes.

## Summary

Tell the user:
- What version was tagged on `main`
- That the pipeline is running: validate → VM acceptance → publish
- Where to watch it: `https://github.com/amcheste/<repo>/actions`
- That `main` now equals the new release and `develop` is ready for the next cycle
- If Step 5 flipped the default branch, mention it explicitly (it's the first release)
Loading