Skip to content

docs(sensei): hub views, fix-quota states, and that a fix PR does not close the finding - #15684

Open
Maffooch wants to merge 3 commits into
bugfixfrom
docs/sensei-capability-views
Open

docs(sensei): hub views, fix-quota states, and that a fix PR does not close the finding#15684
Maffooch wants to merge 3 commits into
bugfixfrom
docs/sensei-capability-views

Conversation

@Maffooch

Copy link
Copy Markdown
Contributor

Documentation for the Sensei capability-views work:

  • Describe the Sensei hub's views and the two fix-quota states (none purchased vs quota exhausted), so the two are not conflated.
  • Explain that a Sensei fix opens a pull request and does not by itself close the finding — the finding closes when the fix is merged and re-scanned.

Docs-only: touches docs/content/sensei/fixing_findings.md and sensei_reference.md. Base bugfix; brought current with the bugfix line.

Maffooch and others added 3 commits August 6, 2026 16:40
The Sensei hub's toggle used to mix two questions: "DefectDojo-hosted" and
"In-repo CI" listed onboarded repositories, while "Auto-fix Candidates" and
"Scan Activity" were views across all of them. The hosted/CI choice is now a
scope inside the Repositories view, so document the toggle as the three views it
selects, and say plainly that candidates and activity always cover every
repository.

Also split the two reasons Approve can be disabled. "No fix quota on this
license" and "quota exhausted" are opposite situations with different actions,
and the hub previously reported both as exhaustion — which told a customer with
no quota to wait for a reset that would never come.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016VjaotfrkL2f2QHvhUcbsh
A pull request changes the code, not what is running, so the finding stays open
after Sensei fixes it — and for a finding that came from a cloud account,
merging Terraform changes nothing the scanner reads until the infrastructure
change is applied. The badge now distinguishes "PR open" from "PR merged", so
document both states and what actually closes the finding.

Also note that reappearances of an outstanding fix are recognised as the same
issue and do not consume extra fixes, and add both to the troubleshooting list,
where "why is this still open?" is the question people arrive with.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016VjaotfrkL2f2QHvhUcbsh
@Maffooch Maffooch added this to the 3.2.300 milestone Aug 17, 2026
@Maffooch
Maffooch requested a review from blakeaowens as a code owner August 17, 2026 03:57
@github-actions github-actions Bot added the docs label Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant