GitHub Integration

GitHub integration enables powerful features like repository cloning, pull request creation, and issue-triggered automations.

Integration Types

Cheffed uses two GitHub integration methods:

Type	Purpose	Required For
OAuth	User authentication, personal repos	Basic repo access
GitHub App	Organization repos, webhooks	Automations, org access

GitHub OAuth

OAuth connects your GitHub account to Cheffed.

Connecting OAuth

1. Go to Settings in the sidebar
2. Find the GitHub section
3. Click Connect GitHub
4. Authorize Cheffed in the GitHub popup
5. Return to Cheffed - your account is now connected

OAuth Permissions

Cheffed requests these OAuth scopes:

Scope	Purpose
repo	Read/write access to repositories
read:user	Read your GitHub profile
user:email	Access your email address

What OAuth Enables

With OAuth connected, you can:

• Clone personal repositories into sessions
• Create branches and commits
• Push changes to your repos
• Create pull requests

GitHub App

The GitHub App provides webhook integration for automations and access to organization repositories.

Installing the GitHub App

1. Go to Settings in the sidebar
2. Find GitHub App section
3. Click Install GitHub App
4. Select your organization or personal account
5. Choose which repositories to grant access
6. Complete the installation

App Permissions

The Cheffed GitHub App requests:

Permission	Access	Purpose
Repository contents	Read & Write	Clone, read files, push commits
Issues	Read & Write	Read issues, post comments
Pull requests	Read & Write	Create PRs, read PR data
Webhooks	Write	Receive events for automations

What the App Enables

With the GitHub App installed:

• Access organization repositories
• Receive webhooks for automations
• Post comments on issues and PRs
• Create pull requests from sessions

Repository Access

Selecting Repositories

During sessions, you can select from:

1. Personal repositories (via OAuth)
2. Organization repositories (via GitHub App)

Only repositories you have access to will appear.

Repository Cloning

When you connect a repository to a session:

1. Repository is cloned into the session container
2. Full git history is available
3. Agent can read, modify, and commit files
4. Default branch is checked out

Working with Branches

Agents can:

• Create new branches
• Switch between branches
• Commit changes
• Push to remote (with your permissions)

Pull Request Creation

Agents can create pull requests from session work:

Automatic PR Creation

Configure your agent to create PRs automatically:

After making changes, create a pull request with:
- Clear title describing the change
- Description explaining what was done
- Reference to related issues

PR Details

Created PRs include:

• Title - Descriptive summary
• Body - Explanation of changes
• Base branch - Target branch (usually main)
• Head branch - Branch with changes
• Reviewers - Optional reviewer assignment

Issue Integration

Reading Issues

Agents can access issue data:

• Issue title and body
• Labels and assignees
• Comments and reactions
• Related PRs

Posting Comments

Agents can comment on issues:

• Analysis findings
• Status updates
• Questions for clarification
• Resolution summaries

Automations with GitHub

GitHub events can trigger automations:

Issue Triggers

Automate on issue events:

• New issue created
• Issue labeled
• Issue edited

PR Triggers

Automate on PR events:

• PR opened
• New commits pushed
• PR merged

See Event Triggers for configuration details.

Troubleshooting

OAuth Not Working

Problem	Solution
Can’t connect	Clear browser cache, try again
Missing repos	Check repo visibility and permissions
Token expired	Reconnect GitHub in Settings

GitHub App Issues

Problem	Solution
App not installed	Complete installation in GitHub
Missing org repos	Install app on the organization
Webhooks not firing	Check app installation permissions

Permission Errors

If you see “Permission denied” errors:

1. Verify OAuth is connected
2. Check GitHub App is installed on the repo
3. Confirm you have write access to the repository
4. Try reconnecting OAuth

Security Considerations

Token Storage

• OAuth tokens are encrypted at rest
• Tokens are only used for authorized actions
• Tokens can be revoked at any time

Revoking Access

To disconnect GitHub:

1. Go to Settings
2. Click Disconnect next to GitHub
3. Optionally revoke access in GitHub settings

Audit Trail

All GitHub actions are logged:

• Repository clones
• Commits and pushes
• PR creation
• Comments posted

Next Steps

• Set up AI Providers for your sessions
• Create Automations with GitHub triggers
• Learn about Cloud Providers for deployments