96
edits
GitHub: Difference between revisions
Jump to navigation
Jump to search
updating private repo directions to avoid confusion
Cknowles-moz (talk | contribs) (→I want a new action/app added to an org: Added verbiage around repo level for apps, org level for actions to the template.) |
Cknowles-moz (talk | contribs) (updating private repo directions to avoid confusion) |
||
| Line 26: | Line 26: | ||
=== I need a private repo created === | === I need a private repo created === | ||
Being an open source company, Mozilla tries to do things in the open. However, the need for private repositories is clear for various non-public data and other business reasons, and in order to track them, please request private repositories using this [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_ignored=0&bug_severity=--&bug_status=NEW&bug_type=task&cf_fx_iteration=---&cf_fx_points=---&comment=I%27ve%20read%20all%20of%20the%20%5Brepository%20creation%5D%5B1%5D%20section%2C%20and%20want%20to%20request%20a%20private%20repository.%20I%27ve%20filled%20in%20all%20the%20required%20fields.%0D%0A%0D%0AOrg%20for%20repo%3A%20REQUIRED%0D%0AName%20of%20Repository%3A%20%20REQUIRED%0D%0ALink%20to%20your%20people.m.o%20entry%20with%20verified%20GitHub%20login%3A%20REQUIRED%0D%0A%0D%0A%5BData%20Classification%5D%5B2%5D%20of%20data%20in%20repo%3A%20REQUIRED%0D%0AOther%20business%20justification%20for%20private%20repo%3A%0D%0AWhen%20can%20the%20repository%20be%20made%20public%3F%20REQUIRED%0D%0ANote%20-%20This%20is%20not%20to%20say%20%22it%20will%20DEFINITELY%20go%20public%20on%20that%20date%22%20but%20more%20%22when%2C%20if%20at%20all%2C%20can%20we%20ask%20about%20possibly%20making%20this%20public%3F%22%0D%0A%0D%0A%5B1%5D%3A%20https%3A%2F%2Fwiki.mozilla.org%2FGitHub%23Do_I_need_to_be_an_owner_to_create_repositories.3F%0D%0A%5B2%5D%3A%20https%3A%2F%2Fwiki.mozilla.org%2FSecurity%2FData_Classification%0D%0A&component=Github%3A%20Administration&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&filed_via=standard_form&flag_type-4=X&flag_type-607=X&flag_type-800=X&flag_type-803=X&flag_type-936=X&form_name=enter_bug&groups=mozilla-employee-confidential&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=mozilla.org&qa_contact=cknowles%40mozilla.com&rep_platform=Unspecified&short_desc=Request%20for%20a%20Private%20Repository%20in%20the%20ORGNAME%20GitHub%20organization&target_milestone=---&version=other template]. <br /> | |||
Be sure to answer all questions marked 'REQUIRED' in the form. As well as the ORGNAME in the title. This lets us know what the repo is for, who needs access, all so that we don't lose track of the private repo | |||
<div id="github_transfer_bug"></div> | <div id="github_transfer_bug"></div> | ||
| Line 189: | Line 190: | ||
{{note|Remember that all repositories must comply with the [[GitHub/Repository Requirements]].|reminder}} | {{note|Remember that all repositories must comply with the [[GitHub/Repository Requirements]].|reminder}} | ||
As the creator, you will automatically have "admin" permissions on the repository. Repository Admins are responsible for the security settings of the repository. This includes approving (or not) requests for GitHub Apps to be added to the app. | As the creator, you will automatically have "admin" permissions on the repository. Repository Admins are responsible for the security settings of the repository. This includes approving (or not) requests for GitHub Apps to be added to the app. | ||