Hello @EdsonDEV ,  Thanks for the screenshot—your Linked accounts page is showing “Error fetching credentials,” which blocks linking GitHub and can make the settings view spin indefinitely.

What typically causes this

• A broken or stale linked Git credential (for example, a PAT that expired or a credential key that no longer exists) can surface as “Error fetching credentials / key does not exist in workspace.”
• Using the Databricks GitHub App (OAuth) with a GitHub EMU account isn’t supported; EMU users must link with a personal access token (PAT) instead.
• A PAT that lacks required scopes (at minimum, repo and workflow if you use Actions) will fail validation when Databricks tries to use it.
• If your org enforces SAML SSO in GitHub, the PAT must be explicitly authorized for SSO or Git operations will be denied.
• Having multiple GitHub sessions in the browser can cause odd auth/UI behavior; using an incognito window or separate browser profile avoids session collisions.

Fast troubleshooting steps

Open the settings in an incognito window (or another browser), then go to Settings > Linked accounts and click Retry to reload the credentials.

• Decide your auth path:

  • If you’re on GitHub EMU, choose Personal access token and avoid the GitHub App.
  • If you are on GitHub.com or GitHub AE (not Enterprise Server), the GitHub App (OAuth) is recommended; otherwise use PAT.
• For PATs, create a fine‑grained token with at least:

  • Repository access limited to the repos you need, and
  • Permissions: Contents = Read and write; include workflow if you use Actions. Then paste it under Settings > Linked accounts and Save.
• If your org uses GitHub SAML SSO, open the token’s details and click Authorize for SSO, then Save again in Databricks.
• If the banner persists and you previously had a bad or expired PAT, you may have a corrupted/ghost credential record. This is a known class of issue; Support can clear the bad key on the backend when the UI can’t load or remove it.

Notes and references

• Setup flow and options (OAuth vs PAT), EMU limitation, and scopes are documented in Databricks docs under “Configure Git credentials & connect a remote repo.” * The Linked accounts page is the right place to add/edit Git credentials for Git folders (Repos).