Skip to content
VEKTIS

Connecting your repository

Connecting a repository takes about two minutes. Once it’s done, every PR you merge into the branch you’ve designated as your release branch will be classified and proposed as a Dev Item.

Before you start

Section titled “Before you start”

You’ll need:

  • Admin access to VEKTIS (so you can open Settings → Integrations).
  • Permission to install a GitHub App on the GitHub organization (or personal account) that owns the repository you want to connect. If you’re not sure, your GitHub org admin can grant it or install on your behalf.

Connect the repository

Section titled “Connect the repository”

  1. Open Settings → Integrations. You’ll see a GitHub section showing Not connected.

  2. Click “Connect GitHub”. You’ll be taken to GitHub to authorize the VEKTIS app. GitHub will ask which account or organization to install it under, and which repositories to grant access to. You can choose a single repository or all repositories — VEKTIS only acts on the ones you select inside its own settings, so granting access to all is safe.

  3. Approve and return to VEKTIS. GitHub redirects you back to Settings → Integrations. The GitHub section now shows Connected along with the GitHub account or organization name.

  4. Pick the repositories you want VEKTIS to track. A list of repositories that the app can see appears. Select the ones whose PRs should generate Dev Item suggestions.

  5. Set the release branch for each selected repository. This is the branch you merge into when you ship — usually main or production. PRs merged into other branches are ignored. The default is main; change it if your team uses a different convention.

  6. Save. The integration begins listening for new merged PRs immediately. There’s no backfill — only PRs merged from this point forward will appear as suggestions.

Verify it’s working

Section titled “Verify it’s working”

After saving, the GitHub section in Settings → Integrations shows:

  • Connected with the account/organization name.
  • The repositories you selected, each with its release branch.
  • A health summary — last received update, number of repositories listening, number of pending suggestions.

The first PR your team merges into a tracked release branch will appear in the Suggested Dev Items section on the Dev Items page within a minute or two.

What gets read, and what doesn’t

Section titled “What gets read, and what doesn’t”
What VEKTIS readsWhat VEKTIS does NOT read or do
PR title, description, labels, base branch, merge timestampSource code, file diffs, individual commit contents
Release tag and publish dateIssue comments, PR comments, review comments
Repository name and the list of branchesAnything outside the repositories you select
Write or modify anything in your repository

Changing what’s connected later

Section titled “Changing what’s connected later”

Anything you set up here can be changed without disconnecting and starting over:

  • Add or remove repositories — re-open Settings → Integrations and update the selection.
  • Change a release branch — if your team renames the default branch or starts shipping from a different one, edit the branch field for that repository.
  • Disconnect entirely — click Disconnect. Existing suggestions are preserved (they don’t disappear); the integration just stops listening for new merges. Reconnecting later picks up where it left off, with no duplicate suggestions for PRs already processed.

Next steps

Section titled “Next steps”

You’re set up. The next time your team merges a PR into a tracked release branch, head to the Dev Items page to see your first suggestion. From there: