Re: [soci-users] Changing the default branch in the Github repository?

[Sebastian L. <seb...@gm...>]

Hi all,

I'd like to recommend /against/ this. There are two major implications:

- All PRs will default against `develop`, which is what you're asking,
- Upon cloning, the checked-out branch will be `develop`.

There are a number of reasons why I'd recommend against this:

- This can break a number of tools that automagically pull against the
repository; I don't know how much of a concern this is regarding SOCI,
but I've heard of some workflows that get broken when this is the
case. I'll see if I can dig up some links on this.
- Most users who just want the source code don't necessarily need to
know what the development workflow is. As soon as you start tracking
the `develop` branch, you *know* that you're going to be using fairly
specific user scenarios. I'd wager that there are a lot more SOCI
users than developers.

I'm a believer in the idea that the default branch should be a stable
one. The only branch guaranteed to be stable in gitflow is master.
Furthermore, there are very little advantages to changing the default
branch: developers who submit PRs get two perform two lesser clicks,
with the adverse effect being potential confusion, and potential
breakage.

I'm sure there's a greasemonkey script somewhere that would allow you
to automagically select `develop` rather than `master`.

My 2 cents,

-S.