Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭 适合新手
  • 哪里不对？
#1,117 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@sadhana-s-codez 已经在做这个了。

开始于 2026年10月28日。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
76/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown
领域
documentation

调研方向

阅读 CONTRIBUTING.md 的“Open a pull request”部分，以及 aidd_docs/memory/vcs.md 的“Setup”和“Branches”部分，并比较 setup、doctor、check 和 reload 目标在 Makefile 中，看看它们是否假定有 push 权限。把 fork 路径（fork、clone、添加 upstream、从 next 拉出分支、推送到 fork、目标为 next）写进这两个文件。完成的标准是两个文件陈述相同的 base-branch 规则，并且 node scripts/check-markdown-links.js 在更改过的文件上通过。

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
TypeScript
星标
481
派生
45
平均合并
1 天 3 小时
30 天内合并 PR
100

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

ai-driven-dev/framework 的其他 Issue

查看 ai-driven-dev/framework 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。