OFFSET偏移
← All reading paths

DOSSIER 22 / 3 ARTICLES

GitHub repositories and collaboration

Move from remote hosting to repository governance, then complete a contribution that can be reviewed.

Start with the first article

Follow the question further.

Git manages commits, branches, and history; GitHub manages hosting, issues, PRs, reviews, permissions, and rules; gh provides a terminal interface. This topic progresses from using repositories to maintaining them and contributing. If you already know Git branches and remotes, start with the contribution workflow. Maintainers should continue to the Actions topic to implement quality gates as platform checks.

  1. 01

    Distinguish clone, fork, branch, and origin/upstream first, then follow the full command sequence to confirm the different boundaries of pushing and creating a PR.

    GitHub basics

    Distinguish Git, GitHub, and gh, then work through sign-in, forking, pushing, and creating a PR.

    Read article
  2. 02

    Start with community files and permissions, then verify the platform state of rulesets, required checks, and releases. Documentation alone does not mean a rule is active.

    GitHub repository management

    Establish repository documentation, permissions, merge rules, and releases as a verifiable governance contract.

    Read article
  3. 03

    Follow issues, topic branches, PRs, reviews, checks, and cleanup, paying particular attention to base/head, shared branches, and history rewriting.

    The GitHub contribution workflow

    Move from issues and branches through PR review and checks to synchronization and cleanup after merging.

    Read article
← More reading pathsAll articles ↗