Suppress Git checkout messages #47

Closed
opened 2023-03-08 08:20:05 +00:00 by badPointer · 4 comments
badPointer commented 2023-03-08 08:20:05 +00:00 (Migrated from git-old.n64.cc)

Git checkout messages muddy ncc installation logs.

Extracting archive /var/ncc/cache/ekelYpVJDj0nYigo/log-1.0.1.zip
Warning: Note: switching to '1.0.1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 8bbafd6 Added PSR
Git checkout messages muddy ncc installation logs. ``` Extracting archive /var/ncc/cache/ekelYpVJDj0nYigo/log-1.0.1.zip Warning: Note: switching to '1.0.1'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c <new-branch-name> Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false HEAD is now at 8bbafd6 Added PSR ```
badPointer commented 2023-03-08 08:20:22 +00:00 (Migrated from git-old.n64.cc)

changed title from Git checkout{-s-} messages{- are not suppressed-} to {+Suppress +}Git checkout messages

changed title from **Git checkout{-s-} messages{- are not suppressed-}** to **{+Suppress +}Git checkout messages**
netkas commented 2023-04-03 15:32:22 +00:00 (Migrated from git-old.n64.cc)

As described in the message, as far as I'm aware the only way to suppress that message is by altering the configuration file for git. However, I don't want ncc to be making changes to the user's configuration file. So I propose two solutions

  • Figure out a way to create a sperate git configuration file for ncc to use only (There may be consequences by doing this, I'm not sure if git treats authentication differently, eg; ssh)
  • Give a warning to the user or a automated prompt to fix this upon the request of the user, so ncc doesn't modify configuration values without the user's permission.
As described in the message, as far as I'm aware the only way to suppress that message is by altering the configuration file for git. However, I don't want ncc to be making changes to the user's configuration file. So I propose two solutions - Figure out a way to create a sperate git configuration file for ncc to use only (There may be consequences by doing this, I'm not sure if git treats authentication differently, eg; ssh) - Give a warning to the user or a automated prompt to fix this upon the request of the user, so ncc doesn't modify configuration values without the user's permission.
netkas commented 2023-04-03 15:32:25 +00:00 (Migrated from git-old.n64.cc)

assigned to @netkas

assigned to @netkas
badPointer commented 2023-04-05 13:53:12 +00:00 (Migrated from git-old.n64.cc)

Maybe just route all STDIN to /dev/null or a logfile?

Maybe just route all STDIN to /dev/null or a logfile?
netkas (Migrated from git-old.n64.cc) closed this issue 2023-10-10 23:51:31 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Nosial/ncc#47
No description provided.