GitScrum + Git Workflow: How Do You Actually Connect Commits to Tasks?

[renatomarinho]

GitScrum tracks tasks. Git tracks code. The gap between them is where things get messy.

What's your workflow for keeping commits connected to GitScrum tasks without extra overhead?

The options:

• Task IDs in commit messages? (e.g., "fixes #GS-142: login bug")
• Branch naming conventions tied to task numbers?
• PR descriptions that reference GitScrum tasks?
• Just... not connecting them and relying on sprint context?

Integration questions:

• How do you handle multiple commits for one task?
• What happens when one commit touches multiple tasks?

Code review flow:

• How do PR reviews map to GitScrum task status?
• Who moves tasks to "Done"—the dev or the reviewer?
• How do you track "code complete but not deployed"?

For teams with complex branching:

• Feature branches, hotfix branches, release branches—how does GitScrum fit?
• How do you visualize what's in production vs. staged vs. in-progress?

The real question:
What's the LEAST amount of process that keeps code traceable to tasks without making devs hate their lives?

Share your Git ↔ GitScrum workflow. Bonus points if it's actually simple.