On Fri, Jun 26, 2020 at 02:58:17PM -0700, Elijah Newren wrote: > The error doesn't need to come that late; it could come at the "init" > step when no branch name is specified. If that's desirable, a > necessary first step towards that would be making a plain "git init" > throw a warning that we are creating a repo with a default branch name > of <whatever> since the user didn't specify one. > > Of course, we could decide to only take that first step and never > escalate it to an error. It'd still leave us with some default name, > but would de-emphasize it some. > > Not sure if I'm in favor of either of these ideas or not, but just > thought I'd point out alternate possibilities towards > removing/de-emphasizing the default initial branch name. Yeah, I agree those are all possible options. My issue is that not picking a default means the user is forced to do so before continuing, which seems fundamentally unfriendly to me. It's putting more friction between the user and their goal. The warning version doesn't force that choice, but then I don't think that's it really accomplished that much. We've still got to have a default, and now we have an annoying warning on top. :) -Peff
