Merged
Conversation
- Introduced a new document outlining best practices for creating minimal diffs, timely commits, and focused pull requests. - Emphasized the importance of clear outcomes per change set and discouraged scope expansion with unrelated edits. - Provided guidance on when to commit and how to structure pull requests for better reviewability and reduced integration pain.
LeviXIII
approved these changes
Mar 31, 2026
dadukhankevin
approved these changes
Mar 31, 2026
Contributor
dadukhankevin
left a comment
dadukhankevin
left a comment
There was a problem hiding this comment.
looks good!
we might want to add claude code and codex equivalents but for now it's fine and those of us who use them can just point them to this file anyway
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
3 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.
No description provided.