Can branching ever be considered a bad practice? [duplicate]
Possible Duplicate:
To branch or not to branch?
Is a merging strategy like Git Flow really an anti-pattern?
My company is using Git, and is using a peculiar branching scheme – work is done in master, and branches are reserved for releases. This works fine, so long as all of the work done in an iteration makes it into the branch, but if a critical production issue comes up, we have to ensure that the work somehow makes it into both branches.
Is it a good practice to have a remote branch for each developer?
Is it considered a good practice to have a remote branch for each individual developer in the project?
Is git-flow in the spirit of git? [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
How to deal with undesired commits that break long-running release builds?
We ran into an unfortunate situation at work recently and I’ve been wondering what we can do to avoid similar problems in the future.
Beta-testing app good practice [duplicate]
Should I halt development of the app during beta-testing?
how to stay efficient when a build is almost always broken
I work in a middle sized team which shares the same source code and while have a continues integration in place, but as all of us has to work in the same branch, the build is almost always broken.
how to stay efficient when a build is almost always broken
I work in a middle sized team which shares the same source code and while have a continues integration in place, but as all of us has to work in the same branch, the build is almost always broken.
Git: rebasing and keeping current to a remote branch – accepted practices?
When developing on a long-running branch (here defined as living longer than one release), what’s the most accepted practice(s) to keeping the branch current with its origin while keeping the history relatively clean prior to merging back?
Feature branches, beta branches, and scrapped features
I’ve been thinking a lot about best practices regarding branching in distributed version control systems such as git an mercurial (the two dvcs’s I have experience with and use on a daily basis).