Skip to content

Commit ac6b689

Browse files
committed
Update 2025-12-25-six-rules-for-pull-requests-that-actually-get-merged.md
1 parent 2d9d9d9 commit ac6b689

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

_posts/2025-12-25-six-rules-for-pull-requests-that-actually-get-merged.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,5 +55,4 @@ The tooling around code reviews is evolving rapidly. [Jared Palmer's recent twee
5555

5656
Tools like [Graphite](https://graphite.dev) have been pioneering this workflow, making it possible to break large features into small, reviewable chunks without the coordination overhead. The race is heating up—Cursor recently acquired Graphite, and GitHub is adding native stacked diff support. It's clear that the industry recognizes a fundamental truth: in the AI age, where we can generate code faster than ever, we need better review tooling to keep pace.
5757

58-
The six rules above still apply, but the tooling is finally catching up to make them easier to follow. What is your "Golden Rule" for Pull Requests?
59-
58+
The six rules above still apply, but the tooling is finally catching up to make them easier to follow. What is your "Golden Rule" for Pull Requests?

0 commit comments

Comments
 (0)