mail-react: Drop the per-feature README convention - #6217
Open
VPS-Ricky wants to merge 1 commit into
Open
Conversation
Agents proposed a README edit on nearly every code change, and those edits almost always had to be reverted by hand. Nothing in the files was both non-obvious from the code and harmful to lose — the rationale was already in TSDoc, test names, commit bodies, or the agent skill.
VPS-Ricky
force-pushed
the
mail-react/drop-feature-readme-convention
branch
from
August 19, 2026 14:04
adae387 to
21f450f
Compare
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.
Agents proposed a README edit on nearly every code change, and those edits almost always had to be reverted by hand. Nothing in the files was both non-obvious from the code and harmful to lose — the rationale was already in TSDoc, test names, commit bodies, or the agent skill.