• 3
    Unless you're pushing working and documented code.
  • 8
    @Berkmann18 Not even then, always branch it and pull from the branch
  • 2
    Wise words my friend
  • 2
    @wellitonpaiva had to learn it the hard way
  • 3
    @corjaantje this is why I hate GitHubs PR system. People think that by using a PR they're not touching master. You are. It creates a culture of fear around deploying software. Deployment shouldn't be scary. It should be boring and something that you don't even really think about because of how easy it is to do.

    My recommendation: don't commit directly to master. Merge into master often, anytime you have code working.
  • 5
    First rule of software development:
    Never touch the master branch.

    Second rule of software development:

    It's a poster that hangs on my wall.
  • 2
    @jimmeh I need a poster like this!!!
  • 3
    If you are like me and you don't understand how use Git correctly, use **Git Flow**!
  • 1
  • 3
    Well if you practice continues deployment then the idea of branching is bad. My opinion is always commit to master so you don't delay the integration, but!! you should have all the quality gateways in place like unit testing, integration testing, cucumber, some form of code inspection and all automated in the build. The idea: fail hard and fail fast so you can fix and deploy.
  • 1
    My philosophy
    4 branches

    Only work in local. Development only gets merged into from local. Staging from development. Master from staging.
Add Comment