git
Block 4.1: Using GitHub to its Full Potential
Tip
Each issue get’s its own number (e.g. #12). When you reference an issues commit number with a keyword like “fix”, it will automatically be closed.
Overview of the issues page in a GitHub repository
Repository: https://github.com/CorrelAid/datenguideR/
View of a single issue on GitHub
Repository: https://github.com/CorrelAid/datenguideR/
forking
themOverview of the pull requests page in a GitHub repository
Repository: https://github.com/CorrelAid/datenguideR
View of a single pull request on GitHub
Repository: https://github.com/CorrelAid/datenguideR
Right now, the VSCode GitHub repository has >5000 issues and almost 400 PRs
Repository: https://github.com/microsoft/vscode
trying-out-pr
git status
library.txt
(run any git
command with -h
)When collaborating, it can often be the case that you want to checkout a branch from a remote locally (e.g. one created by your colleague).
git fetch
to get branchesgit checkout --track <remote>/<branch>
git switch <branch>
team-<your number>
, then push
it to the hosted repoAny Questions?