Skip to content

doc: instructions on how to make membership public #17688

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.

Sign up for GitHub

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

Closed
mhdawson wants to merge 2 commits into from
Closed

doc: instructions on how to make membership public #17688

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a0da3b8
doc: instructions on how to make membership public
mhdawson Dec 14, 2017
3dddd0b
Update onboarding.md
Trott Dec 14, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions doc/onboarding.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,10 @@ onboarding session.
* Branches in the nodejs/node repository are only for release lines
* [See "Updating Node.js from Upstream"](./onboarding-extras.md#updating-nodejs-from-upstream)
* Make a new branch for each PR you submit.
* Membership: Consider making your membership in the Node.js GitHub organization
public. This makes it easier to identify Collaborators. Instructions on how to
do that are available at
[Publicizing or hiding organization membership](https://help.github.com/articles/publicizing-or-hiding-organization-membership/).

* Notifications:
* Use [https://github.com/notifications](https://github.com/notifications) or set up email
Expand Down