This repository has been archived by the owner on Aug 13, 2024. It is now read-only.
generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Finalizing Github setup for new team members #12
Labels
B: Documentation
👤 PM
Role: product manager tasks
⏳ <6 hrs
Size: 1 HfLA week or 1 traditional work day
Milestone
Comments
@cconner57 @lorenzejay @hanapotski @qiqicodes @nasimbiglari @BobbyBishopUX @irisxie @daniellex0 @rcurtis2 @anekkk @AdesinaBernard @ahoang94 Please confirm that you have set up 2 Factor Authentication setup on your Github accounts. |
Profile is public and 2 factor is set. |
Done! |
just got 2 factor auth setup |
Both task done ✓ |
Public and 2-factor authentification activated |
3 tasks
@ExperimentsInHonesty Are you able to check off the last action?
|
6 tasks
Needs to be checked in the next Stakeholder/PM meeting - #89 |
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
B: Documentation
👤 PM
Role: product manager tasks
⏳ <6 hrs
Size: 1 HfLA week or 1 traditional work day
Overview
All team members need to have 2 Factor Authentication setup on their Github accounts. And it is good (but optional) if they have their Hack for LA membership marked public.
Action Items
Once you have accepted (invite comes via email), please do the following:
Mark your own membership public
https://help.github.com/en/articles/publicizing-or-hiding-organization-membership#changing-the-visibility-of-your-organization-membership
Setup two factor authentication on your account
hackforla/governance#20_
The text was updated successfully, but these errors were encountered: