LEARN. PRACTICE. GROW.Concept and mechanism
Git records versions in a repository; GitHub adds hosting, review, and work coordination. A local commit can exist without network access and still be unavailable to colleagues. Push publishes references and objects to the remote. The index contains the version prepared for commit: if you edit a file after add, the later edit does not enter a plain commit until staged again. Fetch obtains remote references without itself integrating content into the current branch. These distinctions help explain differences among the editor, local history, and what a reviewer sees. Shift handover should identify the branch, published commit, and work not yet merged.
Guided application
In a fictional APS incident, separate a timeout fix from extensive documentation restructuring. Coherent branches and PRs allow independent decisions to be reviewed and reversed. A draft PR enables early feedback but does not establish delivery. If conflicts occur, reconcile behavior and validate the result rather than blindly choosing the newest file. A Markdown checklist communicates declared progress; automated checks retain their own evidence. After merge, deleting the working branch does not erase PR discussion. Organizations and teams support continuity through individual identities. GitHub Desktop supports local work; Mobile is useful for triage, comments, and notifications when project execution is unnecessary.
Local commit at 18:00, push still pending: the next shift does not have that change remotely.
Common pitfalls
Commit as push; add as continuous editing; draft as delivered; checklist as CI; branch name as content.
Related topics: Repositories, guidance files, and maintenance · Conversations, traceability, and sharing · Automation, development environments, and AI
Communicate actual change state and evidence available to its recipient.
Reference: GitHub flow · GH-900 skills measured January2026;study guide updated2026-02-19