Most failures name the cause in a notification. NABS Confidence: Show Log opens the Output channel. The gear in that panel can set the level to Debug.
Install and the Retros view
What you see
What to check
The view says to open a folder
Use File > Open Folder… on the repository, then click the rocket again.
No retros, and you expected some
The default folder is team/retros. If the team moved it, set nabsConfidence.retrosFolder to match. In a workspace with several folders, the extension uses the folder of the active editor, or else the first folder that already has retros.
An old copy of the extension is still installed
Uninstall any package that is not nabs.nabs-confidence. The id changed once. Settings kept the nabsConfidence prefix, so they carry over. Copilot may ask for permission again. Choose Allow.
You cannot find it in the Marketplace
It is not published there. Install the .vsix. See Getting started.
Git and GitHub
What you see
What to check
Not a Git repository, or no Git insights
Open the repository root, and check that git works in a terminal. Insights cover the history of the branch you have checked out.
No github.com remote
git remote -v needs an origin on github.com. Without it, GitHub insights, action-item issues and archiving are off. The rest still works. GitHub Enterprise is not supported.
Not signed in
Run Analyse / Refresh Insights and accept the GitHub sign-in. Manage the account from the Accounts menu.
GitHub lists look short
Issues, pull requests and discussions are capped at 50 of each kind.
The Retro Archive category cannot be created for you
GitHub’s API does not offer that. A maintainer creates the category, then you click Re-check. See Archive.
Remove files is refused
The retro’s files, including the front matter just written, must be committed and pushed. The panel says which check failed.
Copilot
What you see
What to check
No GitHub Copilot language model
Install and enable GitHub Copilot Chat, sign in, and check that a model can be chosen in Chat.
Permission to use the language model was not granted
Run the command again and choose Allow, or open Accounts, your GitHub account, Manage Language Model Access.
@retro does not appear
Copilot Chat has to be installed and enabled.
You expected an assessment and there is none
Copilot does not assess when you open a page. Run Assess Objectives with Copilot, with nabsConfidence.useAI on.
Summarise did not change a section
If the section’s start and end markers were removed, that section is left as you wrote it. The notification says so.
Feedback, dates and panels
What you see
What to check
An entry shows as Other
Its type id is not in the retro’s feedback template. Add the type back, or edit the entry.
The entry changed since you opened it
Someone else, or a pull, edited it. Close the form and open the entry again.
My feedback is not in the shared file
The default is one file per person, under <date>-retro.feedback/. Anonymous entries, and shared mode, use the single .feedback.md file.
Feedback will not save
The facilitator has moved past Gather, so feedback is locked. They can go back to Gather to unlock it.
New retros still use the old headings
A customised .template.md with the headings typed in literally will not follow the feedback template. Use the heading placeholders.
Home’s Start button ignored the suggested date
That is the current behaviour. The form opens on today’s date. Set the date before you create the retro. Home still shows the suggestion, so you can copy it.
A panel closed with unsaved changes
A notification offers to restore them for this session. They are not kept across a window reload.
A setting warning on startup
That setting was skipped, or the default was used. Open Settings and correct it. The settings page lists every key.
Limits of this version
One retro per date. The period cannot end after the retro date.
Prepare and Gather are the only guided dashboard stages.
No leadership digest, and no trends across retros.
No un-archive, and a posted Discussion is not updated when the retro changes later.
GitHub Enterprise is not supported, including for shared template repositories. Those are re-checked at most hourly.
People in different time zones can see an item at the edge of a day fall on the other side of the period. Periods use local dates.
NABS Confidence: Report a Problem… is on the Retros view’s … menu and on the Settings panel. It drafts a bug report or a test finding, with your versions and the last lines of the log, for you to check before you send it. You can also copy the same Markdown.
