Repository navigation
docs: route security reports privately - #103
Merged
Merged
Conversation
Keep vulnerability reports out of public issues and request sanitized doctor output for ordinary bugs. Leave blank issues enabled.
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.
Changes
atx doctor --jsonoutput, using the failing command's state override.Doctor JSON does not report OS release or ATX version. The form still asks for those details once, without changing the JSON API.
Checks
scripts/check.sh fullpasses in an owned fresh Cargo target, with 552 unchanged application tests, actual Rust 1.85, docs, dependency policy, package dry run and offline links.PR #101/#102 and the obsolete CodeQL comparison decision remain separate. No settings, analysis deletion, publication or branch cleanup.