News for hackers. Stuff that matters.

PunkPuffin

PunkPuffin on Hacker News

Re:Ask HN: Tangible drawbacks of per-developer Git branches on Friday March 29, 2019 @09:32PM (#19527005)
I feel like if we were to switch to a per-developer system we would end up with something similar to what you described in your last paragraph. But it would develop organically after the system is setup. So by the time we notice that we're back to a per-feature system it'll be too late to change back.....

We ARE using Git, the main reason why I'm dealing with this issue is that someone was tasked to merge different branches and they almost merged incorrect branches because of the similarities in their names. Management was quite displeased after that incident

Ask HN: Tangible drawbacks of per-developer Git branches

Posted by PunkPuffin on Friday March 29, 2019 @08:40PM
from the ask-hn dept.

I happen to be debating an issue at work and I find myself a little bit starved for opinion diversity.The main question : why should I organize my git workflow based on a feature-branch model instead of a developer-branch model?I've been making feature-based branches for as long as I've been using Git, so I never put too much thought into having a different model for my workflow. Moreover, all...

( Read More... | 3 comments | 2 points | on HN )

Ask HN: Tangible drawbacks of per-developer Git branches

Posted by PunkPuffin on Thursday March 28, 2019 @10:21PM
from the ask-hn dept.

I happen to be debating an issue at work and I find myself a little bit starved for opinion diversity.The main question : why should I organize my git workflow based on a feature-branch model instead of a developer-branch model?I've been making feature-based branches for as long as I've been using Git, so I never put too much thought into having a different model for my workflow. Moreover, all...

( Read More... | no comments | on HN )