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
- How to Write a Git Commit Messagecbea.ms
- A Note About Git Commit Messagestbaggery.com
- The ideal PR is 50 lines longgraphite.dev
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- Writing commit messageschiark.greenend.org.uk
- How To Do Lessalexturek.com
- Conventional Commitsconventionalcommits.org
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Keep a Changelogkeepachangelog.com
- To get better at technical writing, lower your expectationsseangoedecke.com
- How to Contribute to Open Source | Open Source Guidesopensource.guide
- First Timers Only - Get involved in Open Source and commit code to your first project!firsttimersonly.com