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

chore: create pull_request_template.md #7726

Merged
merged 3 commits into from
Dec 17, 2021
Merged

Conversation

jennijuju
Copy link
Member

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 changelog based on it
  • check that tests and documentation for the codes that changed are included

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.

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.
@jennijuju jennijuju requested a review from a team as a code owner December 2, 2021 03:37
@jennijuju jennijuju changed the title Create pull_request_template.md chore: create pull_request_template.md Dec 2, 2021
@jennijuju jennijuju requested a review from arajasek December 2, 2021 03:39
@codecov
Copy link

codecov bot commented Dec 2, 2021

Codecov Report

Merging #7726 (52fbee6) into master (0cfc344) will decrease coverage by 0.09%.
The diff coverage is n/a.

Impacted file tree graph

@@            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     
Impacted Files Coverage Δ
extern/sector-storage/worker_tracked.go 76.53% <0.00%> (-8.17%) ⬇️
chain/events/observer.go 71.64% <0.00%> (-6.72%) ⬇️
chain/rand/rand.go 57.89% <0.00%> (-6.32%) ⬇️
chain/actors/builtin/miner/diff.go 52.94% <0.00%> (-5.89%) ⬇️
chain/stmgr/execute.go 86.95% <0.00%> (-4.35%) ⬇️
chain/types/tipset_key.go 85.96% <0.00%> (-3.51%) ⬇️
chain/sub/incoming.go 54.43% <0.00%> (-3.38%) ⬇️
miner/miner.go 54.96% <0.00%> (-2.65%) ⬇️
chain/types/blockheader.go 55.55% <0.00%> (-2.23%) ⬇️
storage/wdpost_sched.go 75.49% <0.00%> (-1.97%) ⬇️
... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0cfc344...52fbee6. Read the comment docs.

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_
Copy link
Contributor

Choose a reason for hiding this comment

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

misc?

Copy link
Member Author

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?

Copy link
Contributor

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.

Copy link
Contributor

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

Copy link
Member Author

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?

Copy link
Contributor

@arajasek arajasek left a 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).

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_
Copy link
Contributor

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.

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_
Copy link
Contributor

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

@jennijuju
Copy link
Member Author

interface breaking change (api, cli and others)
consensus breaking

@jennijuju jennijuju merged commit ec6580d into master Dec 17, 2021
@jennijuju jennijuju deleted the jen/pull-request-template branch December 17, 2021 05:07
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.

4 participants