Guided examples: walk the demo apps through a team's first-week tasks, every step run end to end
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- shell
调研方向
Start by reading demo/setup-local.sh and the planned journeys under tests/acceptance/docs/journeys/, then inspect tests/acceptance/docs/inventory.toml and the docs-journeys workflow. The final walkthrough list and reviewed design must be agreed before implementation because dependent demo-app fixes are still in review. Done means every selected journey has expected results, runs end to end against the demo stack, and is either documented on the page or explicitly marked as not walked.
由索引模型根据 Issue 内容生成。
描述
What
A "Guided examples" page in the user guide. It holds short walkthroughs of what a team does in its first weeks, on the two demo apps that demo/setup-local.sh starts: ShopLab (a storefront) and StreamPulse (a streaming app). Candidates:
- run an A/B test on the storefront, then read its result;
- end the test and ship the winner behind a feature flag;
- roll a feature out in stages, and watch the safety monitor roll it back when crashes spike;
- target a feature by device and app version (web SDK).
The plan sets the final list.
Requirement: everything on the page runs end to end
- Each walkthrough is a docs journey (
tests/acceptance/docs/journeys/), with its expected results written before its first run. - The
docs-journeysworkflow walks every journey against the demo stack. - The page is classed
journeyintests/acceptance/docs/inventory.toml. - Anything that cannot run on the local demo stack is either left out or marked on the page as not walked. That includes the native mobile SDKs, cloud deployment and SSO.
Depends on
The demo-app fixes now in review:
- #1358: late conversions are still sent;
- #1359 and #1362: a paused or completed experiment answers control with a reason;
- the nightly ShopLab journey reading results.
The page describes the behaviour after those merge.
Process
A reviewed plan (design, verification, and the words readers see) comes before any build.
- 主要语言
- Python
- 星标
- 0
- 派生
- 4
- 平均合并
- 5 小时 19 分钟
- 30 天内合并 PR
- 503
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Controlvar/controlvar 的其他 Issue
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 68/100
Controlvar/controlvar#1737 ·
维护者通常 1 天内回复
-
fix(api): the feature-flag list has no defined order across pages可能已有人在做 @amarkanday 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 72/100
Controlvar/controlvar#1612 ·
维护者通常 1 天内回复
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 70/100
Controlvar/controlvar#1562 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 90/100
Controlvar/controlvar#1447 · 2 条评论 ·
维护者通常 1 天内回复
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 72/100
Controlvar/controlvar#1428 ·
维护者通常 1 天内回复
查看 Controlvar/controlvar 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 69/100
jejjohnson/gaussx#752 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
521xueweihan/HelloGitHub#4270 ·
-
enhancement owner: den-haag
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 6 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ok-oldking/ok-wuthering-waves#1828 ·
维护者通常 1 天内回复
-
lesson-submission pending-review
难度 1/5 1 小时以内 新手友好度 65/100
Ikalus1988/MisakaNet#4512 ·
维护者通常 1 天内回复