docs: fix dangling sentence fragment in SECURITY.md#273
Merged
Conversation
Deploying mouseterm with
|
| Latest commit: |
8313441
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://985b818e.mouseterm.pages.dev |
| Branch Preview URL: | https://fix-security-md-dangling-fra.mouseterm.pages.dev |
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
2 participants
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.
Surfaced by the nightly code-quality survey.
SECURITY.md'sTEND_BOT_TOKENbullet had a corrupted sentence — a botched edit left a dangling fragment:The orphan clause "and the bot's trusted identity." followed a sentence-ending period and read as broken prose. The trusted-identity point it was reaching for is already made in full by the bold sentence immediately after ("...but the bot's trusted identity can be used to social-engineer an admin toward a
mainmerge"), so this drops the fragment without losing any content.Docs-only prose fix — no code change and no behavior change, so no test accompanies it. The
security-auditworkflow parses only theFAIL IFbullet lines, so the malformed prose never affected the audit; this is purely readability.