Learn More
Resend Email
3
zedchoo
6y

finally we started adopting gitflow concept and it worked pretty well for most of the projects and devops guy came in saying Gitflow needs to die in a fire because we devops is the best, all the tech companies are using it.

But...

1. gitflow can be tweaked to suit the project's need
2. gitflow can work with devops model
3. our projects are still release based

noooooooooo! gitflow needs to die in a fire! everyone needs to commit directly to master branch now and we CI directly to production!

and some dude started doing so because some random dude said it. wtf?

whats wrong with people?

rant

devops

gitflow
Favorite
Ranter
Comments
  • 0
    6y
    The original flow suggested by nvie doesn't make you commit directly to master, not until you're ready to make a release, you should do your testing on the release branches, you could add a qa branch for final testing aswell.
  • 0
    6y
    @NotWhoIUsedToBe thats what we are doing. but without a QA branch lol but close enough.
  • 0
    6y
    Then i don't get your rant, following a shared set of guidelines makes it easier for everyone.
  • 1
    6y
    @NotWhoIUsedToBe oh, im saying. we had adopted gitflow. and it worked well.

    until someone came in to enforce his understanding of agile and devops then trash our workflow.

    our current workflow is pretty close to devops already. but the guy says gitflow is shit.
  • 0
    6y
    @NotWhoIUsedToBe the guy continued with saying we should just commit directly on master branch, and some other dude started doing so lol
  • 0
    6y
    Oh I'm sorry, it's early here didn't read your rant properly. That sounds pretty horrible
  • 0
    6y
    @NotWhoIUsedToBe the guy commit to master followed gitflow horribly too, merges wrong, never squash etc...
  • 0
    6y
    Don’t worry, I’m sure it won’t be long before someone commits some shit that sneaks through CI and fucks production.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment