Verify real lifecycle project-sync events with pagination and idempotence
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, javascript
调研方向
Read the existing project-sync workflow and its event tests to identify how pagination, stable IDs, live membership, replay, and permission failures are handled. The issue names no file or test path, so first locate those entry points and review dependency #17. Done means the approved sandbox run verifies the listed acceptance criteria; secret placement and the test event set require approval before running.
由索引模型根据 Issue 内容生成。
描述
Goal
Verify the existing project-sync workflow against real events (full pagination, stable IDs, live membership, replay idempotence) and preserve project items and existing label uses.
Observations
- The current workflow already queries all open repository issues and dedupes by project membership; tests exercise actual events, not a new dedup algorithm.
- Local gh scope and secret metadata are not proof of Actions-stored credentials; secret placement is tested manually on an approved sandbox target at runtime.
- No blanket PAT or App support claim is made without validation.
Decision gate
Approve sandbox secret placement and the test event set before running.
Acceptance criteria
- All open issues in the approved sandbox repository are paginated fully and deduped by stable issue/project IDs and live membership.
- Replay is idempotent; project items and existing label uses are preserved with no implicit issue-label migration.
- Any status-approval fixture is human-applied after an exact fixture grant, never automatic.
- Known permission failures warn or skip; unexpected failures are non-zero.
Verification
- Event replay against sandbox -> a single status per issue, no duplicates.
- Secret placement test -> the runtime credential works; local metadata alone is not accepted as proof.
Release checkpoint
Remaining risk: runtime secret wiring is manual and unverified until the sandbox test runs.
Tracking
Roadmap item: B02-03. All acceptance criteria remain pending; publication does not grant approval or release authority.
Dependencies
- Depends on #17 (B02-02).
- 主要语言
- JavaScript
- 星标
- 22
- 派生
- 3
- 平均合并
- 27 分钟
- 30 天内合并 PR
- 27
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
egdev6/github-repository-bootstrap 的其他 Issue
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 25/100
egdev6/github-repository-bootstrap#57 ·
维护者通常 1 天内回复
-
type:docs
难度 1/5 1 小时以内 新手友好度 20/100
egdev6/github-repository-bootstrap#50 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 22/100
egdev6/github-repository-bootstrap#49 ·
维护者通常 1 天内回复
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 25/100
egdev6/github-repository-bootstrap#30 ·
维护者通常 1 天内回复
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 42/100
egdev6/github-repository-bootstrap#29 ·
维护者通常 1 天内回复
查看 egdev6/github-repository-bootstrap 的全部 Issue
相似的 Issue
-
Four problem loader browser tests fail on Windows可能已有人在做 @Patriciaath999 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 85/100
juice-shop/juice-shop#3686 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
TheOdinProject/curriculum#31465 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
TurboDocx/html-to-docx#254 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复