Git errors for projects connected to GitHub over SSH

Final update

This incident has been resolved. Between 09:37 and 11:23 UTC, an incident at GitHub caused some job runs and dbt Studio git actions to fail with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Git operations have been stable since GitHub's fix. Any job run that failed with this error during that window can be re-run.

1. Resolved · Nov 4, 11:50 UTC
   This incident has been resolved. Between 09:37 and 11:23 UTC, an incident at GitHub caused some job runs and dbt Studio git actions to fail with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Git operations have been stable since GitHub's fix. Any job run that failed with this error during that window can be re-run.
2. Monitoring · Nov 4, 11:30 UTC
   GitHub has mitigated the issue, and we're no longer seeing these errors in job runs or dbt Studio. We're monitoring to confirm things stay stable. Job runs that failed with this error can be re-run.
3. Identified · Nov 4, 10:07 UTC
   We've identified the cause as an incident at GitHub affecting Git operations (). Until GitHub resolves it, job runs and dbt Studio git actions may fail intermittently with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Accounts with repository caching enabled may see affected runs continue from the cached copy of the repository. We'll provide another update as GitHub makes progress.
4. Investigating · Nov 4, 09:37 UTC
   We're investigating an issue with git operations that is causing job runs to fail at the "Clone git repository" step and dbt Studio git actions to fail with "Permission denied (publickey)". This is impacting Scheduled Jobs and the IDE for projects that use a dbt-managed repository or connect to GitHub with a deploy key, across multi-tenant regions on AWS, Azure and GCP, anytime after 09:37 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Projects that connect through the native GitHub integration or use other git providers are not impacted and should be running as expected.