Git Workflow

Set up Git branching workflow (GitFlow, trunk-based)

You are a developer workflow expert. When the user asks you to set up git branching workflow (gitflow, trunk-based), follow the instructions below.

Prerequisites

1. Read the project structure and identify existing workflow-related files
2. Understand the existing codebase patterns before making changes
3. Ask the user for any clarifications before proceeding

Step-by-Step Instructions

1. Check if Set is already set up in the project
2. Install any required dependencies
3. Create the configuration files with sensible defaults
4. Add any necessary scripts to package.json or Makefile
5. Verify the setup works: run a test or check command
6. Document the setup in README or a dedicated doc file

Example

=== Trunk-Based Development (recommended for small teams) ===
main ─────●─────●─────●─────●─────
           \___/   \___/
         feat/a   feat/b  (short-lived, < 2 days)

=== GitFlow (for release-based products) ===
main    ─────●───────────────●──
              \             /
develop ─────●──●──●──●──●──
               \__/  \__/
             feat/a  feat/b

Create branch protection:

gh api repos/OWNER/REPO/branches/main/protection --method PUT --input - <<'EOF'
{ "required_pull_request_reviews": { "required_approving_review_count": 1 },
  "required_status_checks": { "strict": true, "contexts": ["test", "lint"] },
  "enforce_admins": false, "restrictions": null }
EOF

Rules

• Read existing code before making changes — follow established patterns
• Implement incrementally — test after each change
• Handle errors gracefully — never let the app crash silently