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
chore(CONTRIBUTING.md): enforce commit guidelines #10748
Conversation
9de93fb
to
8f48718
Compare
I don't like this. |
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 mostly good to me, thanks for formalising this!
We can add a lint script that checks the commit message style as well, so that user has a chance to fix style issues without maintainers nagging about it
Writing guidelines on how commits should preferably be written should be a good idea in any case. |
This is true. We have seen a bunch of PRs of which the subject is not comprehensive. Yes I prefer |
8f48718
to
ff71a31
Compare
I decided to draft this proposal in order to make commit messages more uniform and make history easy to browse. This commit guideline is inspired by Node.js and Arch Linux's commit messages. In case you have any better idea in your mind, feel free to share. After all, it doesn't matter how good the proposal is unless all (or most) of the existing collaborators agree to it. |
My proposal:
And only this. Unnecessarily complex rules are just hard to obey. |
How long should commit message be? |
The suggested rules by @thunder-coding look good to me too. They are following the conventional commit design, which is used by lot of FOSS projects now and also the termux apps repos mostly. Deciding scope as package name is easier here than app components though. |
ff71a31
to
1648463
Compare
5b3b49f
to
5507b8d
Compare
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
5507b8d
to
2af36be
Compare
Lol it's the typo I made earlier, which I fixed somewhere between. It's Anyways it's inspired by Arch's commit messages used in their VCS. |
About adding scripts to lint commit messages, I don't think that's the priority for me now. In case anyone is interested in it, I would be very glad. Atleast I don't expect me to work on it. In case everything seems good, and I get a approving review, I'll format the markdown file, (possibly affecting other lines than the changed ones too), and merge it. |
db1ac92
to
5d28887
Compare
5d28887
to
0b7728b
Compare
Let's finally get this merged. I see a lot do new PRs following similar guidelines, so making it official from semioffical might be worth it :) |
d04d403
to
368cc7b
Compare
What's that? Second typo ;) |
368cc7b
to
dac2045
Compare
So you've been spying on the commit log where you saw the old typo fix :) Anyways fixed. Thanks\ |
When a dev opens a pull request about proper commit messages and then pushes commits with the title |
I'll merge this PR tommorow if there are no changes requested by anyone else. |
d2a72f2
to
24e8822
Compare
Requesting reviews from @Grimler91 @xtkoba @buttaface @MrAdityaAlok.
Feel free to ping any other organization member who'll be affected by this change, or suggest any changes!
TODOs:-