The comprehensive guide to writing the best PR title of all time
graphite.dev · 729 words · saved by 1 readers
The debate around how best to communicate code changes has been raging since punch card programming. Behold! A PR from 1970:
The debate around how best to communicate code changes has been raging since punch card programming. Behold! A PR from 1970: Complete with commit messages: PROJF SLOW VER, GDRAW, PROJF DEMO, XEQ GDRAW, PROJF FAST VER. If these kinds of commit messages look like the ones in your repo… I’m deeply sorry. But there’s still hope! *** Note in this article I'll be using PR title and commit message pretty interchangeably, as I believe that all PRs should only contain one commit. To read more about that check out stacking.dev *** While we’ve come a long way since the 70’s, there’s still a lot of disagr
related reading
- GitHub · Change is constant. GitHub keeps you ahead.github.com
- GitHub - Explosion-Scratch/kdkasad-starred-this-repo: Star to change the repo title to your username! · GitHubgithub.com
- rams - Expert Design Reviews on Every PRrams.ai
- UI Skills for Design Engineers | UI Skillsui-skills.com
- explain-diffgist.github.com
- Semantic Commit Messages · GitHubgist.github.com
- Impeccable: The missing upgrade to Anthropic's impeccable skillimpeccable.style
- Compare · Surfer-Org/Old-Protocol · GitHubgithub.com
- The ideal PR is 50 lines longgraphite.dev
- Prompt guidance | OpenAI APIdevelopers.openai.com
- Discover AI Prompts for Better Results | ShumerPrompt | AI Prompt Marketplaceshumerprompt.com
- Collaborative documents, with powerful AI editing tools | Lexlex.page