Repositories
Connecting a repository gives agents your source code. Agents search and run it in a sandbox. Praxen Inc. assesses each pull request against production and places the repository on the topology next to its deployed resources.
What it does
Agents clone the repository into a sandbox and search it with rg. A function name, an error message or a route points to its exact lines. Agents read files and commits through GitHub. They also run repository code in the sandbox when an investigation calls for it. Every pull request gets an impact assessment against the production topology and a pass or fail comment.
On the topology, the repository is a node joined by deploys_to edges to the resources it deploys and by defines edges to the resources its configuration provisions. When an agent investigates an issue on a service, it follows these edges straight to the code that ships there.
Connect a repository
Open Settings > Repositories in the console and choose Add repository. If GitHub is not connected yet, this installs the Praxen Inc. GitHub app on your organization and lets you pick which repositories Praxen Inc. can read. If it is already connected, it opens the app's settings on GitHub, where you add more repositories. Connected repositories stay in sync as code changes. See GitHub for app permissions.
The repository page
| Tab | What it does |
|---|---|
| Settings | Autofix, impact assessment and sandbox network settings for this repository, described below. |
| Observability | Praxen Inc. reviews the repository after each sync and reports how well its code is instrumented: how many route handlers emit telemetry and which produce none. Each finding can be handed to an agent with Ask Praxen Inc. to fix it. |
| Changes | The history of impact assessments for this repository. Each assessment checks the production topology and returns a pass or fail verdict. |
| Resources | The cloud resources this repository manages. Praxen Inc. links them from deploy manifests and provider metadata. Add any resource it cannot detect with Link resource. Assessments focus on these resources and use the whole cloud account until you link them. |
| Properties | The raw repository record. |
Repository settings
| Setting | What it controls |
|---|---|
| Open autofix pull requests | Whether Praxen Inc. turns confirmed findings into pull requests on this repository. Turning it off stops new ones; existing pull requests stay open. |
| Assess pull requests for production impact | Whether every pull request gets an assessment against the production topology and a verdict comment. |
| Impact assessment instructions | Repository guidance, such as deploy-critical paths and concerns that other checks cover. The agent reads it from preferences/repositories/<owner>/<repo>.md in workspace memory. |
| Block merging on production concerns | Posts the Praxen Inc. production impact check for each assessed pull request. The check fails when an assessment finds a concern. Require it in branch protection to block merging. It is on by default. |
Related
- Impact assessments for what Praxen Inc. checks and how the verdict reads.
- Topology for the graph the repository joins.
- Autofix for the pull requests Praxen Inc. opens against connected repositories.
- GitHub for app permissions and what disconnecting removes.