-
Notifications
You must be signed in to change notification settings - Fork 2
39 how to write a good commit message #41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
First part 'What is a commit?' done. Upcoming updates will include when to commit and how to.
Explains why good commits are important and how to make a good commit title and body detail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added some suggestions
|
I added a small Could you tell me what you think? I can remove it from the post. |
|
@aassuied-ps I think this is ready and am happy to merge now! |
Then I'm fine with that. Thanks a lot! : ) |
Ready for review. I added some callout in the blog post for feebacks on some parts I'm not sure. But everything can be modified if needed.
Feel free to give me your feedbacks. : )
Closes #39