[DEV][LAZY CONSENSUS] Enable github policy to only require approval first time for tvm-tirx
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions
- 领域
- ci-cd
调研方向
Read the discussion about enabling GitHub Actions approval only on the first run for the tvm-tirx repository, including the linked tvm/tvm-ffi precedent mentioned in the issue. The issue asks for consensus before requesting an infrastructure setting change; done means the policy is agreed and the infrastructure request is made.
由索引模型根据 Issue 内容生成。
描述
Hi community:
This is a lazy cosensus thread for enabling github action for tvm-tirx repo. Overall we have been very mindfully setting up the actions so that the workflow finishes fast and skip un-necessary ones when changes are detected to not have code changes.
During the process, we do find that when we get PRs, the approval then check process can cause delays for feedbacks for contributors. Sometimes the first gating tests like lint would greatly benefit from contributor PR directly triggers the CI. We have already done that for tvm/tvm-ffi so i assume it would be low risk requirement.
So this is a thread to seek consensus on changing the github action behavior to "only require approval first time". Please share your thoughts. Given this seems to be less controvesrial, we are going to open it as a lazy consensus thread, which means everyone is welcome chime in, and if nobody objects in 72 hours, we will proceed with a request for infra to update the setting.
This thread is mirrored to dev@
- 主要语言
- Python
- 星标
- 13.9k
- 派生
- 4k
- 平均合并
- 8 小时 5 分钟
- 30 天内合并 PR
- 170
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/tvm 的其他 Issue
-
needs-triage type: bug
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
[Bug] [Relax][ONNX] OneHot does not convert floating-point depth to int64可能已有人在做 @tandede 于 2 天前认领。 未关闭needs-triage type: bug
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
needs-triage type: bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
needs-triage type: bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
[Bug][Relax] ReorderTakeAfterMatmul fails on vector dot products可能已有人在做 @hiyufan 于 12 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
aws-samples/sample-per-model-bedrock#782 ·
维护者通常 1 天内回复
-
Google text documents are base64-encoded twice可能已有人在做 @feiiiiii5 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
coveragepy/coveragepy#2364 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100