GitHub Code Repositories Configuration Guide

Connect your GitHub repositories to Septra by installing the Septra GitHub App. This integration grants your AI technical team (CTO Agent) codebase inspection and automated Pull Request (PR) creation capabilities.

---

1. Overview & Value to Your AI Team

Linking your GitHub repositories empowers your CTO Agent to assist with technical tasks, feature implementations, and bug fixes directly inside your codebase.

Once connected, your CTO Agent can:

• Inspect repository folder trees, file structures, and code architecture.
• Read source code files (up to 100KB per file view) to analyze features and diagnose bugs.
• Create feature branches, commit code modifications, and open Pull Requests (PRs) on GitHub.
• Assist with technical documentation and developer workflows.

---

2. Prerequisites Before Connecting

1. Septra Workspace Role: Owner or Admin role in your Septra workspace.
2. GitHub Permissions: Organization Owner or Repository Admin access on the GitHub organization/account where the code repositories reside.

---

3. Step-by-Step Connection Instructions

Follow these steps to connect your GitHub repositories:

Step 1: Open Code Repositories Settings

1. Log in to your Septra Workspace.
2. Go to Intelligence → Code Repositories.
3. Click Connect GitHub.

Step 2: Install the Septra GitHub App

1. You will be redirected to GitHub's official application installation page.
2. Select the GitHub Organization or Personal Account where your repositories live.
3. Choose repository access boundaries:
   • All Repositories: Grant access to all current and future repositories in the organization.
   • Only Select Repositories: Choose specific repositories (e.g. frontend-app, backend-service).
4. Click Install & Authorize.

Step 3: Configure Permission Access Mode in Septra

Once redirected back to Septra (/intelligence/code-repos), select the access mode for each connected repository:

• 👁️ Read Only: Allows the CTO Agent to read code files and analyze architecture. The agent *cannot* create branches or open Pull Requests.
• 🛠️ Read + Write (Pull Requests) *(Default)*: Allows the CTO Agent to read code, create git branches, commit code edits, and open Pull Requests for human review.

---

4. Safety & Pull Request Protections

To maintain absolute repository safety and build integrity:

CTO Agent reads codebase → Analyzes issue → Creates feature branch 
  → Commits code edit → Opens GitHub Pull Request 
  → Human Engineer reviews & merges PR

• No Direct Master/Main Commits: The CTO Agent *never* commits directly to your main or master branches.
• Pull Requests Only: All code changes generated by the CTO Agent are submitted as GitHub Pull Requests, allowing your engineering team to run CI/CD tests and perform standard code reviews before merging.
• 100KB Safety Truncation: File view tools limit single-read operations to 100KB to ensure fast performance and token safety.

---

5. Managing & Disconnecting Repositories

• Update Access Mode: Navigate to Intelligence → Code Repositories, find the target repository, and toggle between Read Only and Read-Write.
• Disconnect Installation: Click Disconnect on the repository page to immediately revoke GitHub App access in Septra.

---

6. Troubleshooting & FAQs

Q: Why isn't a specific repository appearing in Septra?

Check your installation settings on GitHub (github.com/settings/installations). Ensure the Septra GitHub App has been granted access to the specific repository under "Repository Access".

Q: Can the CTO Agent push directly to production?

No! The CTO Agent operates exclusively through git branches and Pull Requests. Production deployments remain under your control.