You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve reviewed quite a few pull requests in recent years and I’ve noticed some less-than-ideal practices when it comes to creating merge commits so I thought I’d list some things you can do to make life a little easier for someone reviewing your code.
Make the commit message as useful as possible A lot has been written about how to write good commit messages, but I rarely see the advice applied to merge commits.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
blog/tips-for-creating-merge-commits/
I’ve reviewed quite a few pull requests in recent years and I’ve noticed some less-than-ideal practices when it comes to creating merge commits so I thought I’d list some things you can do to make life a little easier for someone reviewing your code.
Make the commit message as useful as possible A lot has been written about how to write good commit messages, but I rarely see the advice applied to merge commits.
https://www.brandonpugh.com/blog/tips-for-creating-merge-commits/
Beta Was this translation helpful? Give feedback.
All reactions