doc: update onboarding PR landing info#8479
Conversation
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optionsl `Refs:` metadata.
| * Only include collaborators who have commented `LGTM` | ||
| * Amend the commit description. | ||
| * Commits should be of the form `subsystem[,subsystem]: small description\n\nbig description\n\n<metadata>` | ||
| * The first line should not exceed 50 characters. |
There was a problem hiding this comment.
Maybe specify that the description should use the imperative mood.
There was a problem hiding this comment.
I like it, but that gets a little trickier and starts leaking into other docs:
- Commit message formatting requirements are in
CONTRIBUTING.mdand belong there, IMO. This doc should just link to that section (except for metadata format, since that's Collaborator-specific). - The
CONTRIBUTING.mdshould include the imperative mood requirement. I don't think it does right now. So it will need to be updated too. - There may be some discussion around whether using the term
imperative moodwill be well-understood or is completely accurate. We may want to go with something more like "should start with a present-tense verb". Not sure but there seems to be a risk of bike-shedding.
For those reasons, if it's OK with you, I'd prefer to make the whole adjusting-the-requirements-for-the-commit-message thing be a separate pull request. (Feel free to open it yourself if you wish!)
There was a problem hiding this comment.
Commit message formatting requirements are in CONTRIBUTING.md and belong there, IMO.
I agree but in this case I would argue that the whole sentence ("The first line should not exceed 50 characters.") belongs to CONTRIBUTING.md.
That said, I'm totally fine with this as is, it's really nitpicking :)
doc/onboarding.md
Outdated
| * The remaining lines (except for metadata lines) should wrap at 72 characters. | ||
| * Add required metadata: | ||
| * `PR-URL: <full-pr-url>` | ||
| * `Reviewed-By: human <email>` |
There was a problem hiding this comment.
s/human/collaborator name/?
There was a problem hiding this comment.
Yes, I'll change human to collaborator name. Thanks!
|
LGTM |
1 similar comment
|
LGTM |
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optional `Refs:` metadata. PR-URL: nodejs#8479 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed in 4a42ae3 |
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optional `Refs:` metadata. PR-URL: #8479 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optional `Refs:` metadata. PR-URL: #8479 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optional `Refs:` metadata. PR-URL: #8479 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optional `Refs:` metadata. PR-URL: #8479 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Clarify a few items in the onboarding doc about landing a PR. One addition is to include the optional `Refs:` metadata. PR-URL: #8479 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Checklist
Affected core subsystem(s)
doc
Description of change
Clarify a few items in the onboarding doc about landing a PR. One
addition is to include the optionsl
Refs:metadata.