6

Just taken on a new client through my own business. Great news! They pay well, everything seems to run smoothly and they're a great team.

They gave me access to their Gitlab repos and all looked well...until...no branches! They have zero branches to determine what is the current live distributed project, dev project or any of the various other reasons. I don't often use git but this really bugs me!

Comments
  • 1
    Maybe there was only one dev
  • 0
    @thevariableman There are 4 devs but they are expanding and it appears to be a 'it worked this long' type scenario. Hopefully, we can change that over time. Bloody annoying when setting up local environments etc though!
  • 1
    Branches are not good, they are a necessary evil. Maybe they were lucky enough to avoid them.
  • 1
    @Fast-Nop Interesting thoughts. How would you split between production and development?
  • 2
    @HighTurtleDev in my company, we have completely different locations for dev and production. Dev has R/W access to dev, production has only R access to production. In between, there is QA as gateway who have R access to dev and R/W access to production.

    The job of QA is to enforce adherence to our dev processes. If anything is lacking, stuff will not go over to production no matter what.
  • 1
    @Fast-Nop Interesting approach, I'll consider this method in the future. As a sole dev I tend to find my own working method so thank you!
  • 0
    Maybe they're just using tags?
Add Comment