Repository navigation
Record private repository Security findings as labelled issues - #561
Merged
Merged
Conversation
This was referenced Oct 8, 2026
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Security runs record findings as private issues when the advisory API returns 404 and repository metadata confirms the repository is private.
Missing labels receive descriptions; existing labels remain unchanged. Public repositories continue to receive draft advisories. Non-404 failures and a public repository's 404 fail without creating finding issues.
Closes #540
Evidence
cargo test --test security_run a_private_repository_records_each_finding_as_a_labelled_issue_with_the_advisory_body -- --exactfailed because the Security run stopped atgh: Not Found (HTTP 404).After: The same test passes and checks the exact bodies and both labels on two private finding issues.
cargo test --test security_run: 17 passed, covering repeat audits, closed findings after triage, missing and existing labels, public advisories, and failure handling.cargo test --bin thirdshift security::tests: 5 passed.cargo test: 1,525 passed, 0 failed, 1 existing ignored test.cargo check --all-targets,cargo fmt --check, andcargo clippy --all-targets -- -D warningspass.Test seams
Review coverage
The independent Standards and Spec reviews each read all six changed files against
issue-427, pinned at8b775669cb8bbc1bbd815428337ac587477d2151. Standards: 0 findings; Spec: 0 findings. Changed files left unread by either review: none.Both reports, including each axis's final files-read list, are saved in
.thirdshift-review-UF4Iav/standards.mdand.thirdshift-review-UF4Iav/spec.md.Unaddressed findings
Standards
None.
Spec
None.
Merge Danger
Door: two-way
Reverting restores advisory-only recording. Existing finding issues remain available for the Day shift.
Blast Radius: Security
Changes Security finding storage and the test GitHub adapter. No migration is needed.
Built with codex · gpt-6.1-sol · xhigh