Code Repos

The code repos endpoints let you list, create, update, and delete the repository connections attached to a project. A connected repo unlocks code correlation in analyses — turning symptoms in your logs into a pointer at the suspected file, function, or pull request.

Endpoints

How connections are authorized

Each repo connection holds credentials for one of the supported platforms:

The browser-based OAuth and GitHub App install flows happen in the dashboard and aren't part of this API. Once a connection is authorized that way, it's already represented as a record you can read or modify through these endpoints.

The POST and PUT endpoints accept a credentials object directly — useful when you've issued your own personal access token or app password and want to script the connection without going through the browser flow. Where possible, prefer the OAuth or App route from the dashboard: tokens refresh automatically and revocation is one click.

For platform-specific setup walkthroughs, see:

• GitHub setup
• GitLab setup
• Bitbucket setup

Service mappings

A connected repo is most effective once you tell SigSentry which service name in your logs maps to which path in which repo. Service mappings are part of the connection payload — see Service mappings for the concept and POST /v1/config/repos for the field shape.

See also

• Conceptual walkthrough — Code Repositories
• Authentication — required permissions per endpoint
• Errors — error envelope and codes
• Idempotency — for safe retries on POST