-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: create pull_request_template.md #7726
Conversation
This is the very first iteration of the lotus PR template. The goal of adding PR template is to standardize PR requests and encourage contributors to: - come up with good PR descriptions to give code reviewers a clear overview of what's in the PR - have a clear PR title as lotus generates a change log based on it - check that tests and documentation for the codes that changed are icnluded The PR type follows the https://www.conventionalcommits.org/en/v1.0.0-beta.2/. The [contribution guideline](https://github.com/filecoin-project/lotus#contribute) should be updated with how to create a pr after the template is accepted.
Codecov Report
@@ Coverage Diff @@
## master #7726 +/- ##
==========================================
- Coverage 39.59% 39.50% -0.10%
==========================================
Files 640 640
Lines 68326 68326
==========================================
- Hits 27056 26993 -63
- Misses 36631 36680 +49
- Partials 4639 4653 +14
Continue to review full report at Codecov.
|
.github/pull_request_template.md
Outdated
Before you mark the PR ready for review, please make sure that: | ||
- [ ] The PR title is in the form of of `<PR type>: <#issue number> <area>: <change being made>` | ||
- example: ` fix: #1234 mempool: Introduce a cache for valid signatures` | ||
- `PR type`: _fix_, _feat_, _BREAKING CHANGE_, _build_, _chore_, _ci_, _docs_, _perf_, _refactor_, _revert_, _style_, _test_ |
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.
misc?
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.
whats the difference between chore and misc?
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 think of something like "fix lint" as a chore.
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.
Not sure what a BREAKING CHANGE would count as
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 think of something like "fix lint" as a chore.
and misc?
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.
Can we add having reasonable commit messages?
They can be low on description, but shouldn't be "I'm bad at writing code" (using an actual example I've definitely introduced into Lotus commit history).
.github/pull_request_template.md
Outdated
Before you mark the PR ready for review, please make sure that: | ||
- [ ] The PR title is in the form of of `<PR type>: <#issue number> <area>: <change being made>` | ||
- example: ` fix: #1234 mempool: Introduce a cache for valid signatures` | ||
- `PR type`: _fix_, _feat_, _BREAKING CHANGE_, _build_, _chore_, _ci_, _docs_, _perf_, _refactor_, _revert_, _style_, _test_ |
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 think of something like "fix lint" as a chore.
.github/pull_request_template.md
Outdated
Before you mark the PR ready for review, please make sure that: | ||
- [ ] The PR title is in the form of of `<PR type>: <#issue number> <area>: <change being made>` | ||
- example: ` fix: #1234 mempool: Introduce a cache for valid signatures` | ||
- `PR type`: _fix_, _feat_, _BREAKING CHANGE_, _build_, _chore_, _ci_, _docs_, _perf_, _refactor_, _revert_, _style_, _test_ |
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.
Not sure what a BREAKING CHANGE would count as
interface breaking change (api, cli and others) |
This is the very first iteration of the lotus PR template. The goal of adding PR template is to standardize PR requests and encourage contributors to:
The PR type follows the https://www.conventionalcommits.org/en/v1.0.0-beta.2/.
The contribution guideline should be updated with how to create a pr after the template is accepted.