- Why is special configuration needed for EMU users to use GitHub Skills?
- Can we use our existing EMU organization for Skills exercises?
- Are enterprises using Data Residency (
ghe.com) supported? - What is the purpose of the actions allow list?
- Why is GitHub Codespaces required ?
- Why are GitHub Actions required?
- How much will this cost?
- Do I need this for regular non-EMU organizations?
- The copy exercise button suggests a repository name that is already taken. What should I do?
- Can exercises be created in the EMU user handle instead of an organization?
GitHub Skills exercises were designed to be taken in an individual's GitHub account where each user has full control over their settings.
Enterprise Managed User (EMU) accounts often do not have permissions to create repositories under their GitHub handles.
This guide helps you configure your organization with settings that will allow your employees to take the exercises within your organization.
While it is technically possible, we strongly recommend creating a dedicated "learning organization" for all GitHub Skills activities and other training purposes.
This approach isolates learning environments from production work which may differ in security policies and restrictions.
Enterprises using Data Residency on ghe.com are not supported due to critical limitations, the most important being:
- GitHub Actions differences on
ghe.comprevent necessary workflows from running. - Different API's / logging in mechanisms apply to
ghe.comwhich are not described in the exercises
If you choose not to allow all actions in your learning organization, you must explicitly approve every action required to run the exercises.
The allow list specifies the minimum set of actions required for the exercises to function correctly. This list is updated periodically as new exercises are created or existing ones get updated.
Many GitHub Skills exercises rely on GitHub Codespaces to provide a consistent, pre-configured development environment for learners.
GitHub Skills exercises use GitHub Actions for the automated learning experience. The user is guided through the exercise with automated feedback, validation and step by step instructions delivered via GitHub Actions workflows we created.
There is no additional cost to use GitHub Skills other than the standard costs associated with GitHub Codespaces and GitHub Actions usage.
No. If your users have standard GitHub accounts that they own, they can take GitHub Skills exercises without any special configuration, within their own accounts.
Each exercise has a button to "Copy Exercise" which pre-fills the repository name based on the exercise title.
When creating an exercise within an organization, it is a good idea to add a unique identifier to the repository name, such as your name or initials.
For example, if the suggested repository name is skills-getting-started-with-github-copilot, you could change it to skills-getting-started-with-github-copilot-johndoe to ensure it is unique across the organization.
Since GitHub Codespaces are not available for EMU user accounts, exercises that depend on Codespaces should be created within an organization that has Codespaces enabled.