lincc-frameworks / lincc-frameworks/python-project-template
Keep workflows active
还没有人认领这个 Issue。
- 主要语言
- Jinja
- 星标
- 85
- 派生
- 16
- 平均合并
- 6 小时 18 分钟
- 30 天内合并 PR
- 1
描述
Github will disable workflows for inactive projects, and a project goes inactive after 60 days with no commits.
This will stop smoke tests from detecting breaking changes from upstream package updates.
One solution (which I don't like, but I'm just leaving here to show there are automated solutions): https://github.com/marketplace/actions/keepalive-workflow
Alternatively, you have to pay attention to the github notifications and re-activate workflows each time you get an alert that they're being de-activated. From @DinoBektesevic:
Every 60 days or so without a commit, you just have to go to the actions tab and press "Enable worfklow" again. The issue I have with the automatic disable isn't that it happens it's that the notifications are by default enabled just for the person that made the workflow - not all "admins" or "maintainers" of the repo. This is how sometimes these things go by unnoticed unfortunately because people don't subscribe or watch the action (which I don't think you can do). There's an email GA that can be used as a replacement I believe.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先检查仓库的 GitHub Actions 工作流,以及用于检测上游软件包更新所引入的 breaking changes 的 smoke tests。将自动化 keepalive 方案与文档中说明的手动重新激活流程和通知行为进行比较。完成的标准应是,所选方案能够防止工作流在一段时间没有提交后被静默禁用。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github-actions, python
- 领域
- ci-cd, devops
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100