Repository navigation
docs(setup): align steps 1 and 8 with the adopt-release-tools skill #30
Description
🤖 AI text below 🤖
The adopt-release-tools skill (skills/adopt-release-tools/SKILL.md) uses safer commands than docs/repository-setup.md in two places. The docs are the reference for admins adopting by hand, so they should match:
- Step 1, bot credentials. The docs add the repository to the
--reposlists ofRELEASE_BOT_CLIENT_IDandRELEASE_BOT_PRIVATE_KEY.--reposreplaces the whole list, so a list read from one page (30 repositories) or typed by hand can remove the credentials from other repositories. The skill uses GitHub's add-one-repository endpoints instead:gh api -X PUT orgs/Algorithmiq/actions/variables/RELEASE_BOT_CLIENT_ID/repositories/<repository id>and the same undersecrets/RELEASE_BOT_PRIVATE_KEY. - Step 8, the default branch's ruleset. The docs select it with
select(.name == "main"); repositories often name it differently (for exampleProtect main). The skill finds it by its conditions (includehas~DEFAULT_BRANCH,~ALLorrefs/heads/<branch>), and hands organisation rulesets (source_typeOrganization) to an organisation owner. The step should also give the command for a default branch with norequired_status_checksrule or no ruleset ("create one first" has none today).
Activity
robertodr commentedon Nov 5, 2026
🤖 AI text below 🤖
Both items landed with the squash merge of #29 (57a3936): step 1 of
docs/repository-setup.mdadds the repository toRELEASE_BOT_CLIENT_IDandRELEASE_BOT_PRIVATE_KEYby id, one repository at a time, and step 8 finds the rulesets ofmainthroughrules/branches/main, whatever their name, gives organisation rulesets the bypass only (run by an owner), and covers a ruleset without arequired_status_checksrule and a repository with no ruleset.