# GitHub

Git hosting and pull-request collaboration where contributors already work on GitHub.

ID: github
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/github/

## Why: the goal or problem

A public weather widget shows rain forecasts on community websites. Volunteers propose display fixes. Its contributors already use GitHub; accepting their work without giving everyone write access matters more than operating a server.

## How: work toward a solution

A volunteer pushes a branch to their fork and opens a pull request. A maintainer reviews the difference, requests a correction, then merges. The contribution does not enter the main branch merely by being proposed.

## What: the concept

GitHub hosts Git repositories and collaboration. Git records history; GitHub adds review and access tools. Other hosts also offer pull requests. Codeberg may fit nonprofit community priorities; Gitea may fit self-operation.

[Source](https://docs.github.com/en/get-started/start-your-journey/what-is-github)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

Compare the operator, review flow, integrations, costs and migration path. This example chooses GitHub because contributors already collaborate there, not because pull requests are unique to it. Codeberg emphasizes a nonprofit free-software community; Gitea supports operating your own service. GitLab, Bitbucket and Azure Repos may fit existing work systems.

## Applications

A fork lets a weather-widget volunteer publish a proposed branch without direct write permission to the upstream repository. A pull request collects discussion and revisions. Someone with suitable permission decides whether to merge. Review alone does not deploy the widget or prove the change is correct.

## Implementation & cautions

Set permissions and required checks deliberately. Treat outside contribution code as untrusted when configuring automation and secrets. Before adopting a plan, check repository visibility, storage and automation allowances in current terms. Git history can move to another Git host; issue discussions, permissions and automation need a separate migration rehearsal.

## Evidence

- [GitHub: What is GitHub?](https://docs.github.com/en/get-started/start-your-journey/what-is-github) — Git hosting and collaboration around repositories. (Checked: 2026-09-27)
- [GitHub: Pull requests](https://docs.github.com/en/pull-requests/reference/pull-requests) — Proposed branch changes can be discussed, reviewed and merged. (Checked: 2026-09-27)