Commit b0e8a94e84

b0e8a94e84b4854c6643cea243a2120381c5a0bc

parent: 34f139b808

Verified · cmc

cmc <hello@cleberg.net> · 2026-09-22 18:54 UTC

docs: the about starter goes to the repository's default branch

Layout: unified · split

docs/superpowers/specs/2026-09-22-parity-followup-design.md +5 −2
@@ -68,8 +68,11 @@ form). The app does the same.
68- With no `about_path` and `canEdit` true, the section offers "Create 68- With no `about_path` and `canEdit` true, the section offers "Create
69 about file". It runs `repo show <owner>/.gitbay`; on exit 3 (not 69 about file". It runs `repo show <owner>/.gitbay`; on exit 3 (not
70 found) it runs `repo create <owner>/.gitbay`. It then runs 70 found) it runs `repo create <owner>/.gitbay`. It then runs
71 `repo commit-file <owner>/.gitbay profile/README.md --ref main 71 `repo commit-file <owner>/.gitbay profile/README.md --ref <branch>
72 --message "add profile about" --file -` with the web's starter text 72 --message "add profile about" --file -`, where `<branch>` is the
73 existing repository's `default_branch` from `repo show` (the server
74 reads the about file from the default branch) or `main` for a
75 repository just created, with the web's starter text
73 (`# <owner>\n\nThis is the about text on your profile.\n`), and 76 (`# <owner>\n\nThis is the about text on your profile.\n`), and
74 reloads. Any other failure is shown and stops the flow. `repo create` accepts `<org>/.gitbay` from an org admin 77 reloads. Any other failure is shown and stops the flow. `repo create` accepts `<org>/.gitbay` from an org admin
75 (`resolveNewRepoOwner`, `internal/control/repo.go`), so the offer is 78 (`resolveNewRepoOwner`, `internal/control/repo.go`), so the offer is