1. Dokumentationen
  2. GitHub
  3. FAQ - Frequently Answered Questions

Dokumentationen

FAQ - Frequently Answered Questions

Administration

(GHES+GHEC) How do I order a GitHub Organization?

Question: How do I order a GitHub Organization?

Answer: An organization is granted for each organizational unit of the University of Bern. The prerequisite is a technical group in Active Directory. The naming convention and organization administration are based on this. The OU admins are authorized to order an organization and will be registered as its administrators accordingly.

Please submit the organization order via Service Request. Select "GitHub Enterprise" as the technical service.

(GHES) Users cannot be found

Question: Why can some accounts of my organizational unit be found while others cannot?

Answer: Authentication on GHES is done via EntraID. Accounts are created upon their first login and can only be found and invited to an organization or team from that point on. Those who can be found have already logged in to https://github.unibe.ch at least once.
The missing accounts need to be contacted and asked to perform their initial login.

GitHub Copilot

(GHEC) Seats and license types

Question: What license types does GitHub Copilot offer and what do they include?

Answer: For enterprises, you can choose between the plans "Copilot Business" and "Copilot Enterprise". A seat is allocated per user and billed monthly. The choice of plan applies to all seats in an organization; mixing plans is not possible. The plan should be chosen based on the required features and price. The following documents are helpful:

(GHEC) License management

Question: How are GitHub Copilot seats assigned to users?

Answer: Assigning GitHub Copilot seats is the responsibility of the organization owner and is described in detail in the GitHub documentation on the page Setting up GitHub Copilot for your organization.
As described there, activation of GitHub Copilot must first be requested from the IT services via ticket. The following information is required:

  • Name of the GitHub organization
  • OU abbreviation
  • Cost center (REF-XYZ-AB) for billing

(GHEC) Costs and budgets

Question: What costs arise for the organization?

Answer: First, each seat has a fixed monthly price, see Plan comparison. Once the plan's included quotas are exhausted, further usage is billed continuously based on consumption.

Question: What safeguards prevent excessive costs?

Answer: Budgets can be set up to ensure costs do not get out of hand, see

(GHEC) Billing modalities

Question: How does billing of GitHub Copilot seats and costs work?

Answer: Billing is done monthly. The invoice is sent via eForms to the cost center specified by the organization and can be approved there.