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.
A volunteer proposes; a maintainer reviews and merges the weather fix
Public weather widget · contribution example
A proposal crosses the boundary.
Maintainer’s repository
Pull request · proposed change
02Review the diff
03Request correction → contributor updates
04Authorized maintainer merges
main← Accepted rain-label fix
A pull request is a proposal, not write access or deployment. Git history and GitHub review are different layers.
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.
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.
02Applications
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.
03Implementation & 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.
Already talking with external AI? Share this article link and explain why the choice fits your project and which tradeoff matters. Ask how it applies to your agreed requirements.
Discuss this idea
Comments are shared across languages. GitHub login required to post.