| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent b74bc51 commit 08e924e
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -5,14 +5,19 @@ onboarding session. | |||
| 5 | 5 | ||
| 6 | 6 | ## One week before the onboarding session | |
| 7 | 7 | ||
| 8 | - * Ask the new Collaborator if they are using two-factor authentication on their | ||
| 9 | - GitHub account. If they are not, suggest that they enable it as their account | ||
| 10 | - will have elevated privileges in many of the Node.js repositories. | ||
| 8 | + * Confirm that the new Collaborator is using two-factor authentication on their | ||
| 9 | + GitHub account. Unless two-factor authentication is enabled, do not give an | ||
| 10 | + account elevated privileges such as the ability to land code in the main | ||
| 11 | + repository or to start continuous integration (CI) jobs. | ||
| 11 | 12 | ||
| 12 | 13 | ## Fifteen minutes before the onboarding session | |
| 13 | 14 | ||
| 14 | - * Prior to the onboarding session, add the new Collaborators to | ||
| 15 | - [the Collaborators team](https://github.com/orgs/nodejs/teams/collaborators). | ||
| 15 | + * Prior to the onboarding session, add the new Collaborator to | ||
| 16 | + [the Collaborators team](https://github.com/orgs/nodejs/teams/collaborators). | ||
| 17 | + Note that this is the step that gives the account elevated privileges, so | ||
| 18 | + do not perform this step (or any subsequent steps) unless two-factor | ||
| 19 | + authentication is enabled on the new Collaborator's GitHub account. | ||
| 20 | + | ||
| 16 | 21 | ||
| 17 | 22 | ## **thank you** for doing this | |
| 18 | 23 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments