Can't access organization repositories

[thedhruvunde]

cant access my organization's repos, in Github.com section
and when I clone repository by URL section I can't push my changes to origin
It gives some authentication error

[doug-leasure]

The authentication error message is:

---

We were unable to authenticate with github.com. Please enter your username and password to try again.

Username:

Password:

Depending on your repository's hosting service, you might need to use a Personal Access Token (PAT) as your password. Learn more about creating a PAT in our integration docs.

---

This only happens for an organizational account on GitHub.com, not my personal GitHub. I created a PAT with repo-level access and tried using it in the "Password" field of the authentication error dialogue box, but it was not successful.

[Twinki14]

Getting the same issue

[amytimed]

This is quite annoying, I can't access any of my organization repositories.

[skypap]

same issue

[karleinarb]

Same issue here.
Running Version 2.9.4-linux1 (x64)

[amytimed]

This is the only thing stopping me from switching to Linux, and seems to be a common issue, judging by the amount of commenters. Can we please get this fixed?

[bookshiyi]

same issue.

Ubuntu 20.04.3 LTS
Github-Desktop version 2.9.4-linux1 (x64)

[shiftkey]

This is a known issue for the Linux build:

I cannot access repositories under my organization

The GitHub Desktop application is an OAuth application, but this fork does not
have the same permissions as the app does on Windows and macOS, which manifests
in a couple of different ways:

• the "Clone a Repository" view does not show all organization repositories
• pushes to a repository owned by an organization may be rejected with a
  generic error message

The root cause of this is organizations by default will have "OAuth App access
restrictions" enabled, which blocks the GitHub Desktop development app that is
used by this fork.

Workaround: ask your organization admin to approve access
to the GitHub Desktop development app.

#72 (comment) has more context