GitHub
Connect accounts, send trusted builds, recover from permission and rate-limit issues.
- Connect GitHub for handoff
Authorize DriftLess from Account → GitHub so pushes use your token or OAuth connection.
- Pull request vs. push to the default branch
Send to GitHub defaults to opening a PR branch; direct pushes to main require an explicit choice.
- When DriftLess creates a GitHub repository for you
If no project or user default repo is bound, DriftLess may create a private repository using your credentials.
- Why GitHub push says the workspace is not trusted
Delivery-class runs stay preview-only until structural reviewer gates pass—repair the task instead of forcing a broken handoff.
- GitHub rate limits and automatic retries
Heavy Git operations can hit GitHub rate limits; DriftLess may queue another attempt.
- GitHub permissions, organizations, and access errors
Org-owned repositories often need explicit GitHub App approvals; personal repos need fewer steps.
- Disconnect GitHub or switch repositories safely
Rename, move, or delete GitHub repositories only after disconnecting DriftLess bindings to avoid breaking sync state.
- Onboarding repo link vs. Send to GitHub from the Brain
Some project-level GitHub binding flows are paywalled on Free; Brain handoff uses your connected account.