Skip to content
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

docs: Expand commit-message guidelines/examples #5407

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

elwinschmitz
Copy link
Member

@elwinschmitz elwinschmitz commented Jun 12, 2024

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have added tests wherever relevant
  • I have made sure that all automated checks pass before requesting a review
  • I do not need any deviation from our PR guidelines

@elwinschmitz elwinschmitz marked this pull request as ready for review June 12, 2024 08:07
@elwinschmitz elwinschmitz enabled auto-merge (squash) June 12, 2024 08:51
Copy link
Contributor

@aberonni aberonni left a comment

Choose a reason for hiding this comment

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

I like the additions from a content perspective. Given that we are changing this, I also wanna mention that IMHO these considerations are more relevant/important on a PR level rather than on a commit level, especially given that we are using a squash merge strategy.

So, for me, I would replace:
"when committing your changes" -> "when submitting your changes through a PR"
commit message/title/first line -> PR title
commit body -> PR description

@elwinschmitz elwinschmitz merged commit 1c53f41 into main Jun 12, 2024
1 check passed
@elwinschmitz elwinschmitz deleted the elwin/docs.commit-guidelines branch June 12, 2024 14:29
@elwinschmitz
Copy link
Member Author

@aberonni

These considerations on "every commit" do help during code-review, I think. (at least for me writing the PR. :) )

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

Successfully merging this pull request may close these issues.

2 participants