When VEKTIS sees a merged PR, it classifies it into one of five types. The classification drives whether the PR shows up as a suggestion to track in your dashboard. You can use either GitHub labels or a conventional-commit-style title prefix to control the type — VEKTIS reads both.
| Type | What it represents |
|---|
| Feature | A new capability or surface area that customers will notice |
| Improvement | An existing feature gets better — the default when no other type fits |
| Bug Fix | Something that was broken now works as intended |
| Infrastructure | Internal plumbing, tooling, or refactoring with no direct customer-facing change |
| Docs | Documentation, comments, or copy changes |
The classifier checks signals in order and stops at the first match. If nothing matches, the PR is classified as Improvement.
| Priority | Signal | Examples that map to each type |
|---|
| 1 | A GitHub label on the PR (case-insensitive) | feature or enhancement → Feature; bugfix, bug, fix → Bug Fix; infrastructure, chore, infra → Infrastructure; docs, documentation → Docs |
| 2 | A conventional-commit prefix in the PR title | feat: or feat(scope): → Feature; fix: → Bug Fix; chore: → Infrastructure; docs: → Docs |
| 3 | Default | Improvement |
Only the types with measurable customer outcomes become PR suggestions in your dashboard:
| Type | Surfaces as a suggestion? |
|---|
| Feature | Yes |
| Improvement | Yes |
| Bug Fix | Yes |
| Infrastructure | No — typically no measurable customer impact |
| Docs | No — typically no measurable customer impact |
| You see | What to do |
|---|
| A merged PR you’d expect to track but no suggestion appeared | Check the PR’s labels and title — if it ended up classified as Infrastructure or Docs, it was filtered out intentionally |
| Suggestions seem mis-typed | Add a feature, bugfix, or other matching label to future PRs, or adopt conventional commits in titles |
| You want a non-customer-facing change tracked anyway | Skip the auto-suggestion and create a dev item directly — every metric type works the same once linked |
| Most PRs end up as Improvement | That’s the safe default — add labels if you want finer-grained classification, but it’s not required for tracking |