GitHub code workflows

Yodu can connect GitHub as a workspace tool and grant it to an engineering AI employee. Keep the repository as the source of truth for branches, pull requests, reviews, CI, merge rights, and releases.

Connect GitHub

1. Open Tool access → App catalog.
2. Search for GitHub.
3. Start the connection flow.
4. Authorize the intended organization or repository account.
5. Confirm the account appears under Connected.
6. Give the connection a recognizable label when more than one GitHub account exists.

Scope it to the engineering employee

Open Employee access, confirm the GitHub account is enabled for the intended engineering role, and disable its switch for employees whose jobs never touch code.

Start with read or draft-oriented work:

• summarize an issue
• inspect a pull request
• prepare an implementation plan
• write release notes from merged changes
• produce a code-review checklist

Repository writes stop at the approval gate; review the first ones there individually before granting a session allowance.

Keep the task and repository linked

Create a Yodu task with:

• repository name
• issue or pull request URL
• requested outcome
• acceptance criteria
• files or areas in scope
• test expectations
• human reviewer

The task is the business context. GitHub is the code-review and release context.

Recommended repository safeguards

Configure these controls in GitHub:

• least-privilege app or account permissions
• protected default branch
• pull request review requirements
• required status checks
• CODEOWNERS for sensitive areas
• human-controlled merge rights
• environment protection for production

Do not rely on an employee instruction alone to protect the repository.

A safe code workflow

The exact write actions available depend on the connected GitHub toolkit and the granted account permissions.

Sensitive changes

Always require human review for:

• authentication and authorization
• billing and payments
• database migrations
• secrets and environment configuration
• deployment workflows
• destructive scripts
• customer-data access

Review the output

Before accepting code work, confirm:

• the change matches the Yodu task
• the branch or pull request is scoped
• tests ran and results are visible in GitHub
• no unrelated files changed
• sensitive areas have the right reviewers
• the human merge gate remains intact

Troubleshooting

GitHub shows authorizing or connecting

Finish or repeat the authorization flow, then confirm the account under Connected.

The employee cannot read the repository

Check both layers: the connected account must include repository access, and the employee's switch for that account must be enabled.

A write action is blocked

Check the Approvals queue for a pending decision, then the GitHub account permissions. Keep the block when the work should require approval.

CI or branch protection blocks the change

Treat that as the repository policy working. Fix the code or ask the human reviewer to resolve the policy decision; do not weaken branch protection to make the workflow pass.

For GitHub's own security controls, see the official documentation for branch protection and GitHub App permissions.