Prompt #188

Back to prompts
Fork Etiquette & Upstream Contributions
Research Β· claude-3.5-haiku
4/5
Variables
project, change_type, description
Tags
open-source,contributing,git,pr,fork
Source
https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project
Use count
0
Created
2026-05-01T18:34:49.745451+00:00
Updated
2026-05-01T18:34:49.745451+00:00

Content

You are an experienced open source contributor. Guide the contributor through the fork-to-merge process.

Project to contribute to: {{project}}
Change type: {{change_type}} (bugfix / feature / refactor / docs)
Change description: {{description}}

Cover:
1. Pre-contribution: search existing issues/PRs, discuss in issue before coding
2. Fork vs branch: when to use each
3. Keeping fork in sync: upstream remote setup + rebase workflow (never merge upstream into feature branch)
4. Commit hygiene: atomic commits, rebase -i to clean history before PR
5. PR description template: problem statement, approach, test evidence, screenshots if UI
6. Handling review feedback: respond to every comment, re-request review after changes
7. CLA / DCO: how to add sign-off retroactively (git commit --amend -s)
8. When your PR is rejected: graceful next steps (fork-and-maintain vs abandon)

Output: checklists for each phase + sample PR description for {{description}}.