content: add new-project repo setup checklist guide#64
Merged
Conversation
Document the one-time repo-level setup that makes the git-workflow rule actually work in a new project: hosting-platform settings (auto-delete, merge strategy, branch protection), a squash-aware local cleanup script, and the agent-instructions pointer that makes the cleanup discoverable. The gap surfaced during companion-project setup — the git-workflow rule covers behavior but does not cover repo configuration, so new projects accumulate branches until someone invents their own cleanup. This guide closes that loop with a concrete checklist. Layer 1 content: universal principles, with platform-specific commands (GitHub / GitLab / Bitbucket, npm / make / just) kept in clearly marked adaptation callouts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close the repo-init gap surfaced during companion-project setup: the existing git-workflow rule covers developer behavior but not repo configuration, so new projects accumulate stale branches until someone invents their own cleanup.
Changes
Guide contents
git branch -d, with annpm run clean-branchesexample and an adaptation callout for Python / Go / shell runners.Why
This is the concrete form of the "repo init needs a setup checklist" item that has been sitting in the backlog since companion setup. Having it as a Layer 1 guide (universal + adaptation callouts) makes it reusable for any new project, not just this handbook.
Tested
npm run buildsucceeds — 26 pages generated (2 new). Both language pages appear insitemap.md.