GitHub

Why you connect a repository

An investigation can describe a timeline with no code at all. It can point at a line only if it can read the code that was deployed.

That code belongs to one app, so the connection belongs to the project, not to the whole workspace. The agent reads the commit your release reported. It does not read whatever is on the default branch today, unless that is all it has.

Connect it during setup

After you name a project, Setup opens with the repository card first. You can skip it and send events anyway. Come back when you want a report to cite a line.

1. 01

   Connect GitHub

   This installs the Bugwalk GitHub App on the accounts you choose. You pick the repositories it may see. Bugwalk can pull those repositories, run their tests, create one branch, and open a pull request. It cannot push to the default branch, comment, merge, or write to your database.

2. 02

   Pick the repository for this project

   The list is what that installation can reach. Connect is per project. Switch projects in the sidebar to connect a different repository.

3. 03

   Set the release

   In the build, set BUGWALK_RELEASE to the commit SHA. Project, Repositories lists releases and shows the short SHA, or No commit when the release could not be placed.

What access looks like

Access is through the GitHub App, and only on the repositories you grant. Uninstalling the app revokes it. A qualifying report can open a pull request on its own within the monthly allowance. After that allowance is used, a member can ask from the report. Merging stays theirs. Bugwalk cannot push to the default branch, comment, or write to your database.

You can disconnect a repository from the same card, on Project, Setup or Project, Repositories. Pro includes one connected repository. Team includes as many as you have projects for.