Option to disable detached head dialogs

[m35]

Please add an option to disable the dialog asking to checkout/create a branch when in detached head state.

[KindDragon]

You want commit in detached head state?

[m35]

Current behavior when committing while not working on a branch:

• The "Not on a branch" message appears warning that "This commit will be unreferenced when switching to another branch and can be lost."
• There is no way around this message unless a branch is checked out.

Desired behavior:

• Add setting to options: "[ ] Don't show warning when committing when not on a branch (i.e. detached head state)" (or maybe "[X] Show warning when committing when not on a branch (i.e. detached head state)")
• By default, have the setting show the message. Current behavior remains the same.
• If the setting is toggled, the "Not on a branch" message does not appear. This is similar (if not identical) to the behavior when on a branch.

[vbjay]

The reason that is done is so that you don't commit and then loose the
commits because nothing is referencing those commits and git cleans up the
dangling commits. This prevents you from having dangling commits and
having to use the reflog later on.

On Tue, Sep 23, 2014 at 1:10 PM, m35 notifications@github.com wrote:

Current behavior when committing while not working on a branch:

• The "Not on a branch" message appears warning that "This commit will
  be unreferenced when switching to another branch and can be lost."
• There is no way around this message unless a branch is checked out.

Desired behavior:

• Add setting to options: "[ ] Don't show warning when committing when
  not on a branch (i.e. detached head state)" (or maybe "[X] Show warning
  when committing when not on a branch (i.e. detached head state)")
• By default, have the setting show the message. Current behavior
  remains the same.
• If the setting is toggled, the "Not on a branch" message does not
  appear. This is similar (if not identical) to the behavior when on a branch.

—
Reply to this email directly or view it on GitHub
#2460 (comment)
.

Jay Asbury
PC Repair and custom programs $30/hr 1hr min
My Biking Blog http://vbjaybiking.blogspot.com

[m35]

Indeed, that is the reason for the existing dialog. And the reason to have the option to disable the dialog is because you're not a git novice, thus well aware of the implications of detached head state and don't need the incessant reminder.

[vbjay]

Even as a git expert, I can see that mistake happening. It is easy to do
with submodules.

On Tue, Sep 23, 2014 at 11:28 PM, m35 notifications@github.com wrote:

Indeed, that is the reason for the existing dialog. And the reason to have
the option to disable the dialog is because you're not a git novice, thus
well aware of the implications of detached head state and don't need the
incessant reminder.

—
Reply to this email directly or view it on GitHub
#2460 (comment)
.

Jay Asbury
PC Repair and custom programs $30/hr 1hr min
My Biking Blog http://vbjaybiking.blogspot.com

[erik-kallen]

At least, IMO, it should not show the "detached head" warning while in a rebase.

[KindDragon]

Indeed, that is the reason for the existing dialog. And the reason to have the option to disable the dialog is because you're not a git novice, thus well aware of the implications of detached head state and don't need the incessant reminder.

But why you want to commit in detached head state?

[vbjay]

Exactly. I would want to know.

…

On Sat, Apr 8, 2017, 3:01 PM Arkady Shapkin ***@***.***> wrote: Indeed, that is the reason for the existing dialog. And the reason to have the option to disable the dialog is because you're not a git novice, thus well aware of the implications of detached head state and don't need the incessant reminder. But why you want to commit in detached head state? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2460 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADdhsZL3jtnQe6WfX8_KYSrfC79t9wVqks5rt9mggaJpZM4CkYsi> .

[ghanique]

I can think of one scenario where you'd be changing the commits during an interactive rebase... Since that can be tricky I try to avoid it and in the scenarios where I can't I'm ok with clicking the "yes, I want to commit in a headless state"-button. What is somewhat dangerous, in that scenario, is that it also suggests to pull​ or merge or something similar. But since I'm not doing that scenario casually anyway I'm not inclined to push the wrong button.

…

On Sat, Apr 8, 2017, 21:03 Jay Asbury ***@***.***> wrote: Exactly. I would want to know. On Sat, Apr 8, 2017, 3:01 PM Arkady Shapkin ***@***.***> wrote: > Indeed, that is the reason for the existing dialog. And the reason to have > the option to disable the dialog is because you're not a git novice, thus > well aware of the implications of detached head state and don't need the > incessant reminder. > > But why you want to commit in detached head state? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #2460 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ADdhsZL3jtnQe6WfX8_KYSrfC79t9wVqks5rt9mggaJpZM4CkYsi > > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2460 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABser2b2XweGOdMJjYtdzZ33ZSO72-pmks5rt9oSgaJpZM4CkYsi> .

[KindDragon]

I can think of one scenario where you'd be changing the commits during an
interactive rebase... Since that can be tricky I try to avoid it and in the
scenarios where I can't I'm ok with clicking the "yes, I want to commit in
a headless state"-button.

We just need to disable this dialog when repository in interactive rebase state, it's bug.