GitHub integration
ThriveOnDev delivers its work to GitHub as pull requests. An owner or admin installs the ThriveOnDev GitHub App and then chooses the repositories the agent may change. Installing the app alone allows nothing.
Connect GitHub
- Open Settings and select the GitHub station.
- Choose Connect GitHub and install the ThriveOnDev GitHub App on your organization. You can give it all repositories or selected ones.
- Choose Choose repositories and pick the repositories the agent may work in.
Choose repositories and branches
The agent works only in repositories on your allow-list. For each repository you can set which base branches it may target. The default is main. A task that targets anything else stops with Repository not allowed.
If you allow several repositories, tell the agent which one a task is for by adding these lines to the issue:
Repo: your-org/your-repo
Base branch: main
If a repository later becomes unreadable for the app, for example because it was removed from the installation, it shows as Unavailable with a Remove button.
What the agent does in GitHub
- Creates a branch and opens a pull request for each task.
- Pushes fixes to the same pull request after a review asks for changes.
- At release, checks that CI passes and squash-merges the exact commit that was reviewed, then deletes the branch. Release never rebases or rewrites the branch. When the base branch has moved on, a fix-review run merges it into the pull request instead.
If your workspace requires human approval, the pull request waits for an approving review from a person on your team before release. See Review loop and human approval.
Credentials
Each run gets a short-lived GitHub token that is valid only for the repositories your workspace allows. Tokens last one hour and are renewed during a long run only while the repository is still allowed. See Data handling and isolation.