-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Closed
Labels
bugConfirmed bugs or reports that are very likely to be bugsConfirmed bugs or reports that are very likely to be bugspriority-2Bug that affects more than a few users in a meaningful way but doesn't prevent core functionsBug that affects more than a few users in a meaningful way but doesn't prevent core functions
Description
The problem
When you have multiple repositories on GitHub Desktop from different GitHub accounts and you log out and log back in to log in with another account, as soon as you do so, you still get the warning that you are not the owner of that repository and that you need to fork it (even though I literally updated the Git email).
Video:
Video.mp4
Release version
3.5.4
Operating system
Windows 11
Steps to reproduce the behavior
- Clone a GitHub repository with one account
- Log in to GitHub Desktop with another account (DIFFERENT from the one in the repo)
- Make changes to the file in that repository and return to GitHub Desktop
- You will get an error saying that the repository is not yours. Now connect with the account for that repository
- Go to the GitHub account icon and then Update Git Email.
- You will see that the fork warning still appears, requiring you to restart the application to make it disappear.
Log files
No response
Screenshots
No response
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugConfirmed bugs or reports that are very likely to be bugsConfirmed bugs or reports that are very likely to be bugspriority-2Bug that affects more than a few users in a meaningful way but doesn't prevent core functionsBug that affects more than a few users in a meaningful way but doesn't prevent core functions
Type
Fields
Give feedbackNo fields configured for issues without a type.