Repository navigation
chore: align repository configuration comments - #1471
Merged
Merged
Conversation
Signed-off-by: Kevinjohn Gallagher <kevinjohngallagher@hotmail.com>
Owner
Author
|
Polish review: no P1 or P2 findings, no changes pushed.
Merge predecessor: none. |
This was referenced Oct 11, 2026
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.
Closes #1470
Aligns comments in repository and deployment configuration with
DEFENSIVE-CODING.md§7. Removes stale history and duplicate explanations while preserving current security, operator, and deployment guidance. The exact historical fixture exceptions in.gitleaks.tomlremain documented.Runtime configuration is unchanged.
Validation:
git diff --check(passed)No application test suites were run because this change only edits comments.
Merge predecessor: none.
Merge order
#1465, #1471, #1472 → #1473, #1474, #1466
main(8141c39) or between any pair. All six merged in this order ontomaincleanly, and the combined tree passes format, typecheck, lint, file-size and comment-voice checks, the docs build (tree clean) and the documentation suites.docs/output.Merge predecessor for this PR: none.
Conflicts: none.