From: Mervin Guy <mail@mervin.works>
Date: Mon, 10 Apr 2023 19:44:26 GMT
Subject: 'git config --edit' unexpected behavior
Message-ID: <0E8CDEA4-21CC-4CF1-809F-3FE37849ED47@mervin.works>

What did you do before the bug happened? (Steps to reproduce your issue)

- Changed my directory to a git-repo I was working on, using 'cd <directory_name>'. Then I ran 'git config --global -e'.

What did you expect to happen? (Expected behavior)

- I exepected the command to display my current-config file, with all settings included, in my editor.

What happened instead? (Actual behavior)

- My config-file was overwritten and displayed a default-setup message, the config-file was lost after this point.
  I experimented with different ways of activating the command, but they all led to an overwrite of the file.

What's different between what you expected and what actually happened?

- The config-file should've displayed as-was, and no overwrite should've occurred unless explicitly commanded.

Anything else you want to add:

- It should be noted that I've been updating my config-file manually, up until this point. When updating it, I used
 '[subsection] component' rather than 'subsection.component'.

[System Info]
git version: 2.40.0
cpu: i686
sizeof-long: 4
sizeof-size_t: 4
shell-path: /bin/sh
compiler info: gnuc: 12.2
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/ash