Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Git identity prompt always appearing #2558

Closed
@cvande04

Description

@cvande04

Prerequisites

Description

Hello, I am a long-time Atom user but a first-time poster. I ran into a novel bug earlier today regarding the Git package, specifically the Git identity prompt. Please let me know if the description of the problem is unclear in any way:

The Git Identity prompt appears every time I open the Git panel in Atom. It asks me to enter my Git username and email. However, I have run both git config --global user.name and git config --global user.email (including prior to the bug manifesting) and double-checking the config file shows that the values are set properly:

[user]
	name = (my username)
	email = (my email)
[github]
	user = (my username)

For a file in a repository that is initialized on Github, the Git identity panel often (but not always) pre-populates the fields with my username and email as found in the config file. For a file in a repository that has not been initialized, the name and email address fields are blank. Switching between two repositories, regardless of whether they are initialized or not, often (but not always) results in the Git identity prompt reappearing, even if I have just used it to sign in moments before switching, and even if I can initially see the Git panel for a few moments before the identity prompt appears. Sometimes, the identity panel will flicker rapidly back-and-forth between having the fields pre-populated and having them blank over the course of a few seconds. After this, trying to re-enter my username or email in the fields often results in glitches, where the character I typed appears in the field for a fraction of a second before vanishing as if I had hit the backspace key. I have tried everything in the debugging guide, including uninstalling/reinstalling Atom and disabling/re-enabling the Git package, as well as re-entering the git config --global values for name and email and repeatedly restarting my computer.

My guess is that it has something to do with my Git credentials, given that it is the Git identity prompt that glitches and that sometimes the fields are not pre-populated with my name and email as I have them configured, but for the life of me I cannot figure out what it is. Running git config user.name or git config user.email brings up the correct values, regardless of repository. I do not have any local configs (i.e. I do not have git config username without the global flag to set any values in any of the repositories in question). Any help would be appreciated; the bug is interrupting my workflow and (in some cases) preventing me from using Atom's Git interface entirely.

Steps to Reproduce

  1. Open Atom
  2. Open a file from a repository
  3. Open Git tab
    4 (optional). Switch between files in different repositories.

Expected behavior:

Git tab (unstaged/staged changes, commit message field, list of past commits) is displayed.

Actual behavior:

Git identity panel is displayed, sometimes after a few seconds of seeing the Git tab and sometimes not; sometimes with the fields pre-populated with my username and email and sometimes not.

git-issue

Reproduces how often:

95% (occasionally, switching between files of two different repositories that are both initialized will not cause the prompt to reappear).

Versions

Atom : 1.53.0
Electron: 6.1.12
Chrome : 76.0.3809.146
Node : 12.4.0

apm 2.5.2
npm 6.14.8
node 12.4.0 x64
atom 1.53.0
python 2.7.8
git 2.22.0.windows.1
visual studio

OS Name: Microsoft Windows 10 Home
Version: 10.0.19041

Additional Information

I should note that one of the repositories is linked to Heroku, although the error is not exclusive to that one repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions