Should you batch stories in a single commit?
This video explains why each user story should be committed separately rather than batching multiple stories into a single commit. It describes a scenario where one story fails after the batch is merged, requiring a revert and time-consuming code spelunking to identify which changes belong to the rejected story. With a single story per commit, you can quickly revert the single commit without changing files one by one. I also recommend including the story number from tools like Azure DevOps or Jira and adding user story context in the commit message.