Things to think about before requesting a new GitHub Organization:

Important: You must be a Penn State employee (faculty or staff) to request a new GitHub Organization within the Penn State Enterprise.

Please read KB0018581 – About Penn State GitHub Organizations for guidance on naming and owning a GitHub Organization within the Penn State Enterprise.

When requesting a new GitHub Organization within the Penn State Enterprise, you must agree that:

• One of the admins of the org must be a full time faculty or staff person with funding approval to cover any expenses related to the GitHub "for pay" (add-on) features that are not included in the base level service. They will need to submit the form which requires budget numbers for the "Business Area", "Cost Object Department", "Cost Object".
  • For more information on potential related costs please refer to our Penn State GitHub Frequently Asked Questions KB article.
• You will take responsibility for the administration of the organization, including:
  
  • vetting users
  • adding users
  • managing users access
  • removing a user when they should no longer have access
  • reassigning their repos to others (or removing them) when they leave
• You will at all times have at least two owners of your organization who must also follow these rules.
• You will notify GitHub Enterprise Administrators if administration of your Organization changes.
• You will not remove GitHub Enterprise Administrators' psu-ghadmin-bot account which is require for automated administrative tasks.
• You will make sure that your users are aware of and, to the best of your knowledge, follow the GitHub Terms and Conditions.
• You will manage and be responsible for access by non-Penn State users, in consultation with your Penn State users.
  
  • Outside collaborators may be added directly to a repository.
    • If you wish to allow a non-Penn State user in at any other level a Penn State sponsored account is required.
    • In either case, such users will be audited periodically for activity without notice; The Organization Administrator(a) will be notified of the results and any necessary follow up actions.
• You understand that GitHub Enterprise Administrators may check for problems in your Organization without notice, including but not limited to:
  
  • Orphaned repositories
  • Users who are no longer affiliated with Penn State
  • Non-Penn State users with no recent activity
  • Unsecured secrets

If your request is accepted, your GitHub Organization will have the following default settings:

• Base member permission: No permission (members must be added to teams/private repos individually; public and internal repos are accessible). This may be changed by an Organization Administrator.
• Forking of private and internal repos is allowed.
• Repository admins may invite outside collaborators.
• Pages access will be allowed, both public and private.
• Repository admins may change repo visibility.

Request your GitHub Organization using this ServiceNow form.