Skip to content

docs: require main-based worktrees#188

Open
YoungJinJung wants to merge 1 commit intomainfrom
docs/main-worktree-rule
Open

docs: require main-based worktrees#188
YoungJinJung wants to merge 1 commit intomainfrom
docs/main-worktree-rule

Conversation

@YoungJinJung
Copy link
Copy Markdown
Contributor

Summary

Document the standing repository rule that all work starts from main in a fresh git worktree.

  • adds the rule to AGENTS.md for agent-facing guidance
  • updates feature, refactor, and PR shipping skills so workflows begin from a main-based worktree
  • records the same contributor workflow in docs/development.md

Related Issues

No issue. User requested this repository workflow rule directly.

Validation

  • env -u GOROOT make test
  • env -u GOROOT make build
  • git diff --check

Checklist

  • Scope is focused
  • Branch name follows docs/branch-naming-harness.md
  • Documentation harness reviewed (docs/documentation-harness.md)
  • README updated if user-facing behavior changed
  • Relevant docs/ pages updated if workflow changed
  • Tests/validation included
  • Breaking changes documented

No breaking changes.

Document that every repository task must start from main in a fresh git worktree so feature, refactor, and PR workflows do not inherit unrelated branch state.

Constraint: User requested this as a standing rule for all future work.

Confidence: high

Scope-risk: narrow

Directive: Start future implementation, refactor, and PR tasks from a new worktree based on main or origin/main.

Tested: git diff --check

Not-tested: make test/build not run because this is documentation-only.
Copy link
Copy Markdown
Contributor

@amazon-q-developer amazon-q-developer Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR successfully documents the worktree isolation workflow rule across agent skills and contributor documentation. The changes are consistent, properly formatted, and add clear guidance without introducing defects. No blocking issues identified.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

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.

2 participants