-
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
base: main
Are you sure you want to change the base?
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
site/posts/how-to-commit/index.qmd
Outdated
When a change on a program affects the behavior of other programs that also needs to be updated, one commit for all the modifications can be done. Also when you decide to modify both a program and the associated documentation. | ||
|
||
::: callout-caution | ||
#### Need feedbacks. |
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.
looks good to me
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.
looks good to me, too
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.
I removed the callout.
site/posts/how-to-commit/index.qmd
Outdated
When a change on a program affects the behavior of other programs that also needs to be updated, one commit for all the modifications can be done. Also when you decide to modify both a program and the associated documentation. | ||
|
||
::: callout-caution | ||
#### Need feedbacks. |
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.
looks good to me, too
|
||
The detail explains **why** the commit needed to be done, the methodological or technical context, or any relevant information that needs to understand the commit. | ||
|
||
It should contains, when relevant, the source (such as a new version of the statistical analysis plan, a decision taken in a meeting minutes, an email, etc), the impact (a modification on a ADaM dataset will have an impact on the TL&F describing the updated variables) or the associated logic. |
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.
I would also mention in some way that you can link to issues (either inside your git productivity tool - GitHub/GitLab - or outside - e.g. if the sponsor uses a specific issue tracking process, for example for QC issues) in case the "why" is that the update was triggered by some defined process.
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.
I added a sentence about it.
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.
@langkabh let me know if you are happy with this then we can get this merged, thanks!
I added a small Could you tell me what you think? I can remove it from the post. |
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