需求功能对接 Git / GitLab平台，实现需求→评审→PR 闭环
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.7k
- Forks
- 719
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 83
Description
反馈标题
需求功能对接 Git / GitLab 平台，实现需求→评审→PR 闭环
反馈内容
目前 MonkeyCode 的"需求"功能完全独立于外部 Git 平台运行，需求记录仅保存在内部数据库，与 GitHub Issues / GitLab Issues无任何双向同步。 需求缺乏评审流程，无法多人评论、审批流转。需求启动开发任务后生成的代码产出（PR）也没有关联回需求，整个过程无法追溯。
当前机制下，需求是一套孤立文档体系，无法嵌入团队的 Git 工作流。
期望效果
- 需求与 Git 等平台 Issue 双向同步：创建需求时可选择同步到关联仓库的 GitHub/GitLab Issues，外部状态变更可回传，需求列表显示外部 Issue 链接及状态
- 需求评审流程：支持多人评论、修改意见、审批通过/驳回，评审记录可追溯
- 需求产出关联 PR：从需求发起的开发任务生成的 PR 自动关联回需求，需求详情页显示关联 PR 列表及状态；PR 合并后需求状态自动更新
- 全生命周期可追溯：需求的创建、评审、修改、开发、PR、上线全过程有时间线记录
我的 UID
019d0ac0-b9c8-78a0-b062-3a6d27891a0e
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by mapping the existing requirement, GitHub/GitLab integration, review, and PR data flows; completion would need the requested synchronization, review history, PR linkage, status updates, and end-to-end timeline to be traceable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, gitlab, typescript
- Domain
- backend-api-design, devops, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100