GitHub troubleshooting

This page covers the most common things that can go wrong with the GitHub integration. If your situation isn’t here, see the main troubleshooting page or contact us.

My PR suggestions stopped showing

Most likely cause: the GitHub connection has lapsed, the release branch you’re tracking has changed, or recent PRs all classified as types that don’t surface as suggestions.

What to check:

1. Open Settings → Integrations. The GitHub section should show Connected with a recent activity timestamp. If it shows Disconnected or Suspended, see “The connection shows as disconnected” below.
2. Verify the release branch. PR suggestions are only generated from PRs merged into the branch you selected. If your team renamed the default branch or switched to a different release branch, edit the branch field in the integration settings.
3. Check the classification. PRs typed as infrastructure or docs are filtered out by design. If all of your team’s recent PRs use chore:, docs:, or labels like infrastructure, none will surface as suggestions. See How PRs are classified for the full ruleset.
4. Confirm the PR was actually merged. Closed-without-merging PRs don’t generate suggestions. Only merges into a tracked release branch do.
5. Wait a minute. Suggestions usually appear within a minute or two of the merge, but in rare cases it takes longer. If it’s been more than five minutes, move on to the other checks.

The connection shows as disconnected

Most likely cause: the GitHub App was uninstalled from your GitHub organization, suspended, or someone clicked Disconnect in VEKTIS.

What to do:

1. Open Settings → Integrations. Read the status message — it will indicate whether the App is suspended, uninstalled, or disconnected.
2. Reconnect. Click Connect GitHub and run through the setup steps again. Existing suggestions are preserved — you don’t lose anything you’d already promoted or dismissed.
3. If the App was uninstalled on the GitHub side, you may need to re-install it on your GitHub organization first. The Connect flow walks you through this.

Note

If the App was suspended by your GitHub org admin (not by VEKTIS), an admin on the GitHub side will need to unsuspend it before reconnecting will work.

A PR I expected didn’t become a suggestion

Most likely cause: the PR was classified as a non-suggestion type, merged into a different branch, or the repository isn’t in the selected list.

What to check:

1. Was it merged into a tracked release branch? Open the integration settings and confirm the release branch matches where the PR actually merged. Merges into feature branches, hotfix branches, or any branch not configured as a release branch are ignored.
2. Is the repository selected? If the PR is in a repository that isn’t in your selected list, it will never produce a suggestion. Re-open settings, select the repository, and set its release branch.
3. What type was it classified as? Open the PR on GitHub and check the labels and title. PRs typed infrastructure or docs (via labels like chore or prefixes like chore:/docs:) are filtered out. See How PRs are classified.
4. Was it already promoted or dismissed? If a previous merge of the same PR (or an earlier reopen-and-merge) was already handled, VEKTIS won’t re-suggest it.

A PR was classified as the wrong type

Most likely cause: the labels or title prefix sent the classifier in a direction you didn’t intend.

What to do: classification happens once, when the PR merges, and isn’t editable from VEKTIS afterward. To change the outcome:

• For PRs that should have surfaced as suggestions but didn’t (classified as infrastructure or docs when they should have been feature/improvement/bugfix): create the Dev Item directly on the Dev Items page. You can paste the PR URL into the Dev tickets field for traceability.
• For PRs that surfaced as suggestions but shouldn’t have: dismiss the suggestion. (Dismissing is permanent — see Reviewing PR suggestions.)
• For future PRs: nudge your team toward conventions that classify the way you want. The classification rules page lists all the recognized labels and prefixes.

I disconnected by accident

What happens:

• The integration stops listening for new merges.
• Existing suggestions in your list — pending, promoted, and dismissed — are preserved exactly as they were.
• Existing Dev Items already created from suggestions are unaffected.

What to do: click Connect GitHub again and run through the setup steps. Pick the same repositories and release branches you had before. New PR merges will start producing suggestions again. There’s no duplicate-suggestion risk for PRs already processed before the disconnect.

I see “Suspended” instead of “Connected”

What it means: the GitHub App is installed on your GitHub organization, but a GitHub admin has suspended it. While suspended, it can’t read PRs.

What to do: ask your GitHub org admin to unsuspend the VEKTIS App in the GitHub organization’s settings. Once unsuspended, VEKTIS will resume listening for new merges. There’s nothing to change inside VEKTIS itself.

Linked tickets aren’t appearing on a suggestion

Most likely cause: the ticket URLs in the PR description aren’t in a recognized format.

What to check: How PRs are classified — Linked tickets lists the supported URL formats. Bare ticket IDs and GitHub issue references aren’t detected — the description needs a full Linear (linear.app/...) or Jira (*.atlassian.net/browse/...) URL.

If a future PR includes recognized URLs, those tickets will appear automatically on its suggestion. Already-created suggestions can’t be backfilled with tickets after the fact, but you can paste the ticket URL into the Dev Item’s Dev tickets field after promoting.

When to ask for help

If none of the above apply, gather:

• A screenshot of Settings → Integrations showing the GitHub section.
• The PR URL of the suggestion (or missing suggestion) you’re investigating.
• The release branch name configured for the relevant repository.

Then send us the details.