MENU


GitHub

Git gave BookNest a history on your own disk. This chapter puts it on GitHub 29 , where other people can find it, file issues, propose changes through pull requests, and where every push is built and tested by machines you never administer. Git 1,932 is the version-control tool; GitHub is a hosting service built around it that adds accounts, permissions, code review, project tracking, continuous integration (GitHub Actions 29 ), package registries, security scanning and an API for all of it. Git itself stays in Git.

Every command was run for real against GitHub.com with gh 2.101.0 29 and Git 2.55.0 in Ubuntu 26.04 225 under WSL2 6 . The example account is a real personal account, binarybehemoth, and BookNest's repository is the public github.com/binarybehemoth/booknest (https://github.com/binarybehemoth/booknest); substitute your own username. The account belongs to no organization, so organization, team and organization-wide steps are shown from GitHub's documentation and labeled "not run here". Tokens never appear in output; where one would, you see <redacted>.

Accounts and Teams to Forks and Community cover accounts, authentication, the repository and collaboration. Inside an Actions Job to Self-Hosted and Pricing teach GitHub Actions in depth, ending in a pipeline that tests and builds BookNest on every pull request and that Docker extends with a container build. The chapter closes with packages, Pages, security, the APIs, Codespaces 29 , Copilot 29 and GitHub's alternatives.

What you will learn:

Sections