That is a hard one! I'm using both in projects at work and I do see a lot of merit for both workflows. I'm more comfortable with gitflow as that has been my go-to in my three years of professional development. The velocity of trunk-based development is enjoyable, but I think I will have to go with gitflow just based on experience.
As I level up as a developer going forward, I wouldn't be surprised if I shift to trunk-based as my prefered style of git strategy.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That is a hard one! I'm using both in projects at work and I do see a lot of merit for both workflows. I'm more comfortable with gitflow as that has been my go-to in my three years of professional development. The velocity of trunk-based development is enjoyable, but I think I will have to go with gitflow just based on experience.
As I level up as a developer going forward, I wouldn't be surprised if I shift to trunk-based as my prefered style of git strategy.