Git branching
People usually stick with the first solution or approach they find to solve their problem. Best practice is think as the silver bullet for a problem without even thinking about it. When you pick a best practice without thinking you are outsourcing all the decisions and choices to the own who created the best practice. It could be the wrong tradeoffs for your problem.
Why do we use git for software development? We need a way to distribute/decentralize the development of the software without one developer causing issues to another one. After the code was made in isolation, we need to integrate it in the main repository. This is usually made using pull requests.
Pull requests enable you request reviews/feedbacks of your code before adding in the main branch. It also let you discover if your approach break any existing behavior or tests
the size of pull requests matters a lot. Small pull requests are easy and faster to review and have less risky of introductions bugs or regressions.
What is wrong about git flow? What is wrong about develop branch?
https://www.atlassian.com/continuous-delivery/continuous-integration/trunk-based-development
- Feature FlagFeature flag enable you modify software in runtime Temp feature flag it is used while development a big feature to make sure we won't break current behavior, so we can merge fast…
- IDEIDE is at the top of productive for developers If you wanna be productive as a developer you need to master your IDE Make sure your IDE provide good and fast code completion Also…
- IssueIssue is an Atom task. It represent a chunk of work to produce something It can represent a new feature that needs to be implemented It can represent a bug that needs to be solved…
Sign in with GitHub to reply.
Select any passage to quote it.
Comments