Re: git-push branch confusion caused by user mistake
- Date: Mon, 13 Mar 2017 12:49:36 -0700
- From: Phil Hord <phil.hord@xxxxxxxxx>
- Subject: Re: git-push branch confusion caused by user mistake
On Mon, Mar 13, 2017 at 1:55 AM Jacob Keller <jacob.keller@xxxxxxxxx> wrote:
> On Fri, Mar 10, 2017 at 2:13 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> > Phil Hord <phil.hord@xxxxxxxxx> writes:
> >> I think git should be smarter about deducing the dest ref from the
> >> source ref if the source ref is in refs/remotes, but I'm not sure how
> >> far to take it.
> > My knee-jerk reaction is "Don't take it anywhere".
> > Giving a refspec from the command line is an established way to
> > defeat the default behaviour when you do not give any and only the
> > remote, and making it do things behind user's back, you would be
> > robbing the escape hatch from people.
> It might be worth having some warning or something happen here? I've
> had several co-workers at $DAYJOB get confused by this sort of thing.
On one very active project at $work, we have 380,000 commits, 4600
branches in refs/heads and 96 branches in refs/remotes. About half of
the refs/remotes (43) are obviously user errors. The other half it's
not possible for me to know.
I suggested to our admins to block attempts to push to
'refs/remotes/*' so in the future users don't lose track of commits
they think they pushed. But I don't know if that will really happen.
Thanks for the counterexample feedback.