Contributing to claude-ops

PRs welcome from anyone. This document covers the branch strategy, protection rules, and PR workflow.

Branch Strategy

• main is the only long-lived branch and the default branch.
• All work happens on feature branches (e.g., fix/setup-gog-url, feat/stripe-revenue).
• Feature branches are merged into main via PR.
• There is no dev branch.

Branch Protection

main is protected by three layers of rulesets (repo-level + org-level):

Rule	Maintainer	External contributors
Direct push	Allowed	Blocked
Force push	Blocked	Blocked
Delete branch	Blocked	Blocked
Merge PR without approval	Allowed	Requires 1 approval
Unresolved review threads	Allowed	Blocked

These rules are enforced at both the repository and organization level and cannot be overridden by repository settings alone.

PR Workflow

For external contributors

1. Fork the repo
2. Create a feature branch from main
3. Make your changes
4. Open a PR targeting main
5. Wait for review and approval from a maintainer
6. Once approved, a maintainer will merge your PR

For maintainers

1. Create a feature branch from main
2. Push the branch and open a PR targeting main
3. Resolve any automated review comments (Copilot code review runs on push)
4. Merge via gh pr merge --merge --admin

Local Development

# Clone and run in development mode
git clone https://github.com/Lifecycle-Innovations-Limited/claude-ops.git
cd claude-ops
claude --plugin-dir ./claude-ops/claude-ops

# After making changes, reload without restarting
/reload-plugins

Code Review

• Copilot code review runs automatically on every push and may leave review threads.
• All review threads must be resolved before merge (for non-maintainers).
• Maintainers can resolve threads and merge without external approval.

License

By contributing, you agree that your contributions will be licensed under the MIT License.