Prepare to use GitHub with this learning path.
This path has been curated by the GitHub team.
Ever wondered how GitHub works? Let's see how Eddie and his team use GitHub.
GitHub flow is a lightweight, branch-based workflow that supports teams and projects where deployments are made regularly. This guide explains how and why GitHub flow works.
In this video, you will learn how to find the key pages and features in a GitHub repository.
The GitHub Glossary is a great resource for many terms, including the very important version control system used in GitHub: Git.
A part of the book Pro Git, this chapter explains what Git is and how it works as a version control system.
Read the official GitHub documentation about what repositories are, and what features they include.
This chapter of Pro Git is about cloning, an important part of working with Git on your local machine.
Working locally has an interesting challenge of keeping the remote and local repositories update. Git pull and git push are network commands to help.
To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions of your project that are hosted on the Internet or network somewhere.
Use the GitHub flow to track and discuss changes in issues, then propose and review changes in pull requests.
Labels on GitHub help you organize and prioritize your work. You can apply labels to issues and pull requests to signify priority, category, or any other information you find useful.
This article will explore best practices to help you maintain a healthy codebase without impairing collaboration. You will learn when and how to use required status checks, branch restrictions, required reviews and more.
Adopting InnerSource approaches to software development can be transformative but understanding the principles, and potential challenges, is critical to success.
You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions.
A fork is a personal copy of another user's repository that lives on your account.
Open source software is made by people just like you. Learn how to launch and grow your project.
You can sponsor contributors, receive updates on developers and organizations you sponsor, and display a sponsor badge throughout GitHub
Add tools to help you build and grow
GitHub offers free and paid products. You can see pricing and a full list of features for each product at https://github.com/pricing. For information on planned features and products, see the GitHub public roadmap.
With plans for every developer, learn what options are available.
While you can grant read/write access to collaborators on a personal repository, members of an organization can have more granular access permissions for the organization's repositories.
After you create an organization, you should give Owner permissions to a small group of people who will manage the organization account. Learn more about organization permission settings here.
You can customize access to each repository in your organization with granular permission levels, giving people access to the features and tasks they need.
A repository owned by a user account has two permission levels: the repository owner and collaborators.
We all play a role in securing the world’s code—developers, maintainers, researchers, and security teams. On GitHub, teams work together to secure the world’s software at every step.
You can set up your GitHub account to require an authentication code in addition to your password when you sign in.
You should create a personal access token to use in place of a password with the command line or with the API.
Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to GitHub without supplying your username or password at each visit.
With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com.
GitHub Enterprise keeps logs of audited user, organization, repository, and system events. Logs are useful for debugging and internal and external compliance.
LDAP lets you authenticate GitHub Enterprise Server against your existing accounts and centrally manage repository access.
SAML SSO gives organization owners and enterprise owners on GitHub a way to control and secure access to organization resources like repositories, issues, and pull requests
You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect.
All public courses on Learning Lab are free.