docs(framework): explain how a contributor without push access opens a pull request

Open Beginner friendly
  • Is something wrong?
#1,117 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@sadhana-s-codez is already working on this.

Since Oct 28, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Read the "Open a pull request" section of CONTRIBUTING.md alongside the "Setup" and "Branches" sections of aidd_docs/memory/vcs.md, and compare the setup, doctor, check and reload targets in the Makefile to see whether they assume push access. Write the fork path (fork, clone, add upstream, branch off next, push to the fork, target next) in both files. Done looks like the two files stating the same base-branch rule and node scripts/check-markdown-links.js passing on the changed files.

Written by the indexing model from the issue text.

Description

Problem

CONTRIBUTING.md takes a contributor from "Get it validated" to "Open your PR" with one instruction: "Branch off next, target next". It never says what a contributor without write access to ai-driven-dev/framework does to get there. A search for "fork", "write access" and "push access" in CONTRIBUTING.md, GOVERNANCE.md, .github/PULL_REQUEST_TEMPLATE.md and README.md returns nothing.

A community member reported during a community call that they could not open a pull request for a small slides update because they lacked the rights, and stopped at filing two issues. The issue-first path works; the missing step is how a non-maintainer goes from a validated issue to a pull request.

Scope
  • Add a short path for contributors without write access to the "Open a pull request" section of CONTRIBUTING.md: fork, clone, add upstream, branch off next, push to the fork, open the PR against next of ai-driven-dev/framework.
  • Check that make setup, make doctor, make check and make reload run from a fork clone, and state any difference.
  • Give the fork variant of gh pr create where aidd_docs/memory/vcs.md describes the base branch.
Acceptance criteria
  • CONTRIBUTING.md states what a contributor without push access does between "Set up" and "Open a pull request", without leaving the page.
  • Starting from a validated issue and a fork, the documented commands alone lead to an open pull request targeting next.
  • make setup, make doctor, make check and make reload are confirmed to run from a fork clone, or the differences are documented.
  • CONTRIBUTING.md and aidd_docs/memory/vcs.md give the same base-branch rule.
  • node scripts/check-markdown-links.js passes on the changed files.
Prior art in this repo
  • CONTRIBUTING.md, "Open a pull request": branch off next, no fork step.
  • GOVERNANCE.md, roles table: Certified Members validate issues, Maintainers approve and merge.
  • aidd_docs/memory/vcs.md, "Setup" and "Branches": gh pr create without --base next targets production.
  • Makefile: setup, doctor, check, reload already exist.
  • #1114 plans an issue skill, which covers creating issues, not pull requests.
  • #928 covers which validation commands a plan carries, not contributor access.
Out of scope
  • A contributor skill or plugin that automates fork, branch and pull request, and whether it lives in the repository's own .claude/skills or in a marketplace plugin. Not decided; #1114 covers the user-facing skills.
  • Granting write access to contributors: a governance decision, see GOVERNANCE.md.
Dominant language
TypeScript
Stars
481
Forks
45
Avg merge
23h 18m
Merged PRs (30d)
106

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ai-driven-dev/framework

All issues in ai-driven-dev/framework

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.