-
Notifications
You must be signed in to change notification settings - Fork 94
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(maintenance): add project guides #36
Conversation
0a92e9d
to
7285e46
Compare
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.
This is awesome! I have some suggestions though.
MAINTAINERS_GUIDE.md
Outdated
- At least two Collaborators must approve a pull request before the pull request lands. | ||
- PRs with commits that don't follow the [conventional commits standard](https://www.conventionalcommits.org) should be re-written when merging. | ||
- Use Github's _squash and merge_ when landing PRs. | ||
- CI must pass before landing PRs, needless to day. |
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.
typo, needless to say
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.
Good, catch, fixing.
CONTRIBUTING.md
Outdated
``` | ||
- Open the pull request, see details in the template. | ||
- Make any necessary changes after review. | ||
- In order to land, a Pull Request needs to be reviewed and approved by at least one `c8` Collaborator. |
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.
This is different from the maintainers' guide
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 think I can remove this; looks like it's creates confusion...
CONTRIBUTING.md
Outdated
|
||
### Setting up your local environment | ||
|
||
- Make sure you have installed the latest version of Node.js |
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.
just a minor thing, you could just use 1.
for every bullet point and markdown will figure out the numbering, even if we have to add or remove steps later.
CONTRIBUTING.md
Outdated
``` | ||
$ npm run test:snap | ||
``` | ||
- If all is passing, commit your changes following the [conventional commits guideline](https://www.conventionalcommits.org/) |
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'd argue this isn't strictly necessary since the maintainers can do this with the squash and merge function. IME this is a barrier to entry for beginners, so I'd put it in the Maintainers' guide.
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.
Makes sense, will move it.
.github/PULL_REQUEST_TEMPLATE.md
Outdated
- [ ] `npm run test:snap` (to update the snapshot) | ||
- [ ] tests and/or benchmarks are included | ||
- [ ] documentation is changed or added | ||
- [ ] commit message follows [conventional commit guidelines](https://www.conventionalcommits.org/) |
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.
as mentioned below, this can be optional for the contributor and is really up to the merger to enforce with GH's squash and merge function.
@JaKXz -- thanks for the review Jason, fixed 👍 |
7285e46
to
c2f9be3
Compare
CONTRIBUTING.md
Outdated
## Issues | ||
|
||
- You can open [issues here](https://github.com/bcoe/c8/issues), please follow the template guide. | ||
- You can come over to the `node-tooling/c8` channel for discussions, [follow this link](https://devtoolscommunity.herokuapp.com/) to request for an invite. |
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.
minor nit: drop for
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.
Rephrased.
MAINTAINERS_GUIDE.md
Outdated
- At least two Collaborators must approve a pull request before the pull request lands. | ||
- PRs with commits that don't follow the [conventional commits standard](https://www.conventionalcommits.org) should be re-written when merging (squash and merge). | ||
- Use Github's _squash and merge_ when landing PRs. | ||
- CI must pass before landing PRs, needless to say. |
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.
Honestly, if it's needless to say, it doesn't need to be here. I should've said that the first time, sorry.
MAINTAINERS_GUIDE.md
Outdated
|
||
- Label the issues appropriately, see the list of labels and their description [here](https://github.com/bcoe/c8/labels) | ||
- Be welcoming to first-time contributors, identified by the GitHub `first-time contributor` badge. | ||
- At least two Collaborators must approve a pull request before the pull request lands. |
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.
Just curious if @bcoe thinks this project is at that level of maturity already... I wouldn't want to block a contribution waiting for that 2nd review.
Maybe this could be relaxed to should be approved by 1-2 collaborators before merging
? 🤷♂️
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 think 1 is decent; and looks like that's how it has been... rewriting.
Thanks @profnandaa - I have a few more thoughts... sorry for the piece-meal reviews! |
No worries sir :) Will check it out.
-na
On Sun, Sep 30, 2018 at 3:30 AM Jason Kurian ***@***.***> wrote:
Thanks @profnandaa <https://github.com/ProfNandaa> - I have a few more
thoughts... sorry for the piece-meal reviews!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#36 (comment)>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAP8kUxqC2uqxt5-Hrw3eLrLtsvrHPrXks5ugBCmgaJpZM4W4c0u>
.
--
Sent from a tiny device while on the move.
|
- issue template - PR template - contributing guide - maintainers guide closes bcoe#35
c2f9be3
to
fcdc964
Compare
@JaKXz -- thanks, done. |
##### Checklist | ||
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. --> | ||
- [ ] `npm test`, tests passing | ||
- [ ] `npm run test:snap` (to update the snapshot) |
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.
perhaps add here, if any new tests have been added.
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.
this is very good, I'm comfortable landing; @JaKXz any more blockers?
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'm done now, thanks @profnandaa :)
- issue template - PR template - contributing guide - maintainers guide closes bcoe#35
closes #35