I made PR #1295 and you overwrote my commit message. I think we need a rule for commit message to avoid overwriting commit messages. If there is the rule, it could be good for contributors. For example, we need create the rule like below:
What do you think ?
A few points:
@ljharb
it's always acceptable and expected for maintainers to edit commit messages, rebase, squash, etc, upon merging - neither the original commit message nor commit authorship should be expected to be retained (although authorship generally is, out of courtesy)
I understand the necessity of maintainers to edit.
I'd be fine with a PR that documented our commit messages (we'd probably need some back-and-forth on the PR before it was final), although this is the first time it's really come up.
In Airbnb, Is there a rule of commit message ? if it is, I think we can create new one based on existing rule.
No, we don't have any commit message convention that spans projects.
Earlier I created a Git guide at the company I used to work. You can use it as an inspiration:
@ljharb I will create a CONTRIBUTING.md in reference to existing commit log.
@gergoerdosi I appreciate it :smile:
@ljharb I just close it because I am busy now. If I create the PR, I reopen this issue.
Most helpful comment
@ljharb
I understand the necessity of maintainers to edit.
In Airbnb, Is there a rule of commit message ? if it is, I think we can create new one based on existing rule.