Repository history
Keep source files and their commit history together. Branches let you work on a change without editing the main line of development.
Build together with GitHub.
GitHub hosts Git repositories and gives individuals and teams a place to review code, track work, automate workflows, and collaborate on software.
TOOL PROFILE
GitHub
Version control & collaborationGit records how files change over time. GitHub adds a hosted home for Git repositories, plus the collaboration tools teams use to review, discuss, and ship those changes. A repository can hold the application code, its history, and the conversation around proposed updates.
01
What it helps you do
The practical parts of GitHub you are most likely to use.
Pull request reviews
Propose a branch for merging, inspect its diff, discuss specific lines, and record review decisions before it lands.
Issues and planning
Capture bugs and feature work as issues, then connect that work to code changes and project boards.
Automated checks
Use GitHub Actions to run repeatable checks such as tests or builds when code is pushed or a pull request is opened.
02
A practical way to start
Follow a small workflow to get value from the tool without over-configuring it.
- Create or choose a repository Start with a new repository or open one you have permission to access. Check its README and contribution notes before changing a shared project.
- Make a focused branch Create a branch for one feature or fix. Small, focused changes are easier to review and safer to merge.
- Commit and open a pull request Commit your work with a clear message, push the branch, and open a pull request that explains the change and how you tested it.