Changes

Jump to: navigation, search

GitHub

543 bytes added, 14:14, 24 February 2023
Should I make a separate GitHub organization or just create a repository in an existing one?: Added notes around maybe NOT making a new org
=== Should I make a separate GitHub organization or just create a repository in an existing one? ===
With much of Mozilla's GitHub presence in GitHub Enterprise at this point, if you want to create a organization, we'd love to hear from you about it via a [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration bug here], requesting an org to be created and added to our enterprise.
Noting that we already have >50 orgs, so we'd like to make sure you don't already fit into one of the existing spaces.
 
If the org isn't to be related to Mozilla's Enterprise, then the original advice still applies:
This is a personal preference, in general. (Some product lines may have policies about source code locations.) If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details. Additional resources on establishing an organization are:
* [https://mozilla-hub.atlassian.net/l/cp/75n1PWoo Mozilla Standards] <small>''login required''</small>
<div id="forking"> </div>
 
=== Forking vs Transferring ===
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it. There are a number of limitations to just pushing your repo's content into a new repo under mozilla (you loose all GitHub metadata). Refer to [https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/transferring-a-repository GitHub's docs] for details.
86
edits

Navigation menu