FFT-GitHub - Git Workflow and Repository Operations
Overview
Section titled “Overview”FFT-GitHub keeps the repository disciplined. It manages branches, authors PRs, curates issues and milestones, and enforces FlowForge Rules #5 (ticket-first) and #33 (no AI references in git history). Every operation is grounded in the principle that professional git history is what makes time tracking — and therefore developer payment — trustworthy.
Capabilities
Section titled “Capabilities”- Branch strategy: trunk-based, GitFlow variants, release branches, hotfix patterns.
- PR authoring: structured descriptions, linked issues, review assignments, draft-to-ready workflows.
- Commit hygiene: Conventional Commits, rule-compliant messages, interactive rebasing done safely.
- Issue management: templates, labels, milestones, project boards, cross-repo linking.
- Release operations: semver bumps, changelog generation, tag signing, release notes.
- Merge strategy: squash vs merge vs rebase decisions per project policy.
- Rule enforcement: automatic checks for Rule #18 (no direct main commits) and Rule #33 compliance.
- Automation: GitHub Actions, CODEOWNERS, branch protection, required checks.
When to Use
Section titled “When to Use”- Creating a PR from a completed session and preparing it for review.
- Reorganizing a messy branch into a clean, reviewable commit history.
- Setting up branch protection, CODEOWNERS, and required status checks for a new repo.
- Cutting a release: version bump, changelog, tag, GitHub Release.
Example Prompts
Section titled “Example Prompts”"Create a PR from feature/health-check to main with linked issue and review request""Rebase my branch into three logical commits respecting Conventional Commits format""Cut v2.1.0: bump version, generate changelog from commits, and create the GitHub Release"