Skip to documentation content

Sources

GitHub

Capture decisions from merged PRs, labeled issues, and AI-detected code changes.

UpdatedMay 13, 2026

On this page

GitHub connects code changes and issues to decision records.

What GitHub does

  • Connects a GitHub App installation to Verachi.
  • Listens for pull request, issue, label, and review events.
  • Captures decisions from configured labels, merged pull requests, or AI-assisted PR analysis when enabled.
  • Links the created decision back to GitHub.
  • Can feed risk evaluation from pull request and review activity.

GitHub remains the source of record for PR and issue discussion. Verachi reads source content for analysis, then stores the conclusion and source pointer.

Connect GitHub

  1. Open Integrations.
  2. Open GitHub.
  3. Click Connect.
  4. Install the Verachi GitHub App.
  5. Choose the repositories to include.

Create a rule

  1. Open Integrations > GitHub.
  2. Click New rule.
  3. Choose the GitHub behavior.
  4. Enter the GitHub label, such as decision.
  5. Enter the source repository or path.
  6. Choose the Verachi project.
  7. Save.

Capture a decision

Common capture paths:

  • Add the configured label to a pull request.
  • Add the configured label to an issue.
  • Merge a pull request that is detected as decision-worthy.
  • Enable repository AI analysis where supported.

Review created decisions before publishing or relying on them.

What Verachi reads and stores

Reads

  • Pull request or issue title, body, labels, comments, review comments, and repository metadata

Stores

  • Decision record
  • GitHub permalink
  • Verachi-written conclusion and optional rationale
  • Source metadata such as installation ID, repository, PR or issue number, labels, detection method, and confidence when AI is used

Verachi does not store raw PR bodies, issue bodies, comments, review comments, linked issue bodies, repository contents, or patches for integration capture.

Troubleshooting

  • The GitHub App must be installed and active.
  • The repository must be included in the installation.
  • The rule source must match the repository or path.
  • Label capture requires the configured label.
  • AI capture requires repository AI analysis to be enabled.