Skip to content

feat(standards): add the bootstrap of repository settings - #14

Merged
Nain9Dev merged 1 commit into
mainfrom
feat/bootstrap
Oct 14, 2026
Merged

Nain9Dev merged 1 commit into
mainfrom
feat/bootstrap

Conversation

@Nain9Dev

Copy link
Copy Markdown
Member

Summary

Part of task T22 of specs/next-ci-reliability (contrast3d-platform): the bootstrap of a new
repository's settings, decided with the owner (dry run by default).

  • standards/bootstrap.py owner/name [--apply] plans and applies: delete_branch_on_merge, secret
    scanning and push protection on public repositories (free), Dependabot alerts and security updates,
    and the labels automerge and needs-human. Archived repositories are refused; a setting already
    in place is not touched.

Verification

  • 13 new tests with a simulated gh (plan, apply, rendering and the real commands), written first;
    115 in total. ruff clean.
  • Dry run against two real repositories: it reports the missing automerge and needs-human labels
    (the train needs automerge to work) and, in contrast3d-bot, security updates off.

Apply the organisation's settings to a new repository: branch deletion
after merge, secret scanning and push protection where they are free,
Dependabot alerts and security updates, and the automerge and needs-human
labels the merge train uses. A dry run by default, --apply makes the
changes, and a setting that already follows the standard is left alone.
@Nain9Dev
Nain9Dev merged commit caedc2d into main Oct 14, 2026
5 checks passed
@Nain9Dev
Nain9Dev deleted the feat/bootstrap branch October 14, 2026 19:48
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