Repository navigation
chore: en dashes, and credit the perch scan report - #20
Merged
Merged
Conversation
House rule from 10 November 2026: the em dash (U+2014) is not used anywhere. SECURITY.md gains a 'With thanks' section. The policy already offers to credit a reporter by name; this is the first one to credit.
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.
Two things.
En dashes. House rule from 10 November 2026: the em dash (U+2014) is not used anywhere in the organisation's repositories. Mechanical replacement, no wording changed.
A 'With thanks' section in
SECURITY.md. The policy already says "we are glad to credit you by name"; Gianna Gonzales of Perch Scan is the first person to credit. She reported on 6 November that the payment grid truncated past 1,000 transactions and understated amounts owed. She was right, and the same pattern was in six other places including the month-end report – kaffeelisten#62, fixed in kaffeelisten#63.The section also notes why the report counted despite "reports generated solely by an automated scanner" being out of scope: it said what the finding meant for this application instead of quoting a rule number. Worth writing down, because it is the line we will apply to the next one.
No GitHub handle to credit – the report came by email and gave none.