ER: Ensure 'reopened' PRs get checked for properly linked issues
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 76/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, yaml
- 领域
- ci-cd
调研方向
阅读 .github/workflows/pull-request-trigger.yml 和链接的 GitHub Actions 文档。将 reopened 添加到 pull_request 活动类型中，然后验证重新打开 pull request 会触发 workflow，并检查其描述中是否包含关联的 issue。该 issue 还链接了有关设置个人环境的测试指南。
由索引模型根据 Issue 内容生成。
描述
Emergent Requirement - Problem
We should add "reopened" to the types of events on PRS that trigger the pull-request-trigger.yml Github Action. Currently, that Github Action, which checks PR descriptions for keywords and linked issue numbers, is only triggered on "opened" and "edited" events.
Issue you discovered this emergent requirement in
- #8815
Date discovered
10-24-2026
Did you have to do something temporarily
- YES
- NO
Who was involved
@castillios
@daras-cu
What happens if this is not addressed
If a closed PR that is not properly formatted with a linked issue is reopened, it will not be checked by this Github Action and the PR will not get a comment nudging the author to properly link their issue.
Resources
- GitHub's 'Events that tigger workflows', pull_request activity types docs: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request
- For testing Github Actions, refer to https://github.com/hackforla/website/issues/6537#issuecomment-2041147335, especially Tips 6, 7, and 8, if you have not already created you personal environment for testing.
- More notes on testing Gtihub Actions: How to Test GitHub Actions
- Additional Notes for GitHub Actions
Recommended Action Items
- Make a new issue
- Discuss with team
- Let a Team Lead know
Potential solutions [draft]
Issue:
- Complexity: Small (While the suggested change here only requires changing one line of code, I gave it the Complexity: Small label because it requires testing GitHub Actions.)
- Relationships: None
- Size: 0.25pt
- Fix:
in ~/.github/workflows/pull-request-trigger.yml (line 2-4), change:
on:
pull_request:
types: [opened, edited]
... to:
on:
pull_request:
types: [opened, edited, reopened]
- 主要语言
- JavaScript
- 星标
- 365
- 派生
- 872
- 平均合并
- 8 天 19 小时
- 30 天内合并 PR
- 2
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
hackforla/website 的其他 Issue
-
Complexity: See issue making label epic good first issue Issue Making: Level 1 P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
难度 1/5 1 小时以内 新手友好度 62/100
维护者通常 1 天内回复
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
难度 2/5 1-3 小时 新手友好度 67/100
hackforla/website#8871 · 1 条评论 ·
维护者通常 1 天内回复
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: back end/devOps role: front end size: 0.25pt time sensitive
难度 1/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
Complexity: Small ER Feature: Refactor CSS Issue Making: Level 2 P-Feature: Projects page ready for merge team role: front end size: 0.25pt
难度 2/5 1-3 小时 新手友好度 75/100
hackforla/website#8860 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
查看 hackforla/website 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 85/100
githubnext/gh-aw-workshop#5752 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
维护者通常 1 天内回复
-
channels:add check:passed
难度 1/5 1 小时以内 新手友好度 66/100
iptv-org/database#39416 · 2 条评论 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
swisstopo/topo-swisseobrowser#48 ·
维护者通常 1 天内回复