Communicate failed checks back to the author/project
还没有人认领这个 Issue。
评估
调研方向
首先查看 patchwork API 如何接收检查结果，以及 check-generators 如何报告这些结果。在定义传达已完成状态意味着什么之前，先明确预期接收方、交付机制，以及应报告失败还是成功。
由索引模型根据 Issue 内容生成。
描述
In our project, we've had instances of developers being surprised that they had failed checks - or that checks were even happening. Rather than force developers to check a web page when they're used to using email, it would be nice if the patchwork server could send out some form of status when checks fail (or perhaps also when they succeed); either to the patch author or to the project mailing list.
Yes, I know a separate app could poll the patchwork API and send emails as needed, but doing it in patchwork results in more immediate feedback and less processing. Reporting from whatever app is doing the checks would require all check-generators to support email independently, and distribute any configuration requirements.
- 主要语言
- Python
- 星标
- 317
- 派生
- 91
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
getpatchwork/patchwork 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
难度 2/5 1-3 小时 新手友好度 74/100
getpatchwork/patchwork#546 · 2 条评论 ·
-
难度 3/5 1-2 天 新手友好度 52/100
getpatchwork/patchwork#664 ·
-
难度 4/5 3-5 天 新手友好度 48/100
getpatchwork/patchwork#663 ·
-
难度 3/5 1-2 天 新手友好度 45/100
getpatchwork/patchwork#645 ·
查看 getpatchwork/patchwork 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 90/100
learningequality/ricecooker#747 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 76/100
run-llama/llama_index#23199 ·
-
难度 2/5 1-3 小时 新手友好度 84/100
KhronosGroup/glTF-Blender-IO#2769 ·