Skip to content

Conversation

aassuied-ps
Copy link
Collaborator

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

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
@aassuied-ps aassuied-ps linked an issue Sep 3, 2025 that may be closed by this pull request
Copy link
Collaborator

@kieranjmartin kieranjmartin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added some suggestions

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the callout.

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.

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.

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

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!

@aassuied-ps
Copy link
Collaborator Author

I added a small callout-tip part about using AI. I did not implement it to one of my repositories yet. It needs technical skills so I'm not sure an explanation in this blog post is relevant. But I mentionned the fact that it's possible to plug something to review all changes and suggest a commit.

Could you tell me what you think? I can remove it from the post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How to write a good commit message
3 participants