Repository navigation
Open
Labels
Complexity: MediumEREmergent RequestEmergent RequestFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicReady for Prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Milestone
Description
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
Date discovered
10-24-2026
Did you have to do something temporarily
- YES
- NO
Who was involved
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 The "Hack for LA's GitHub Actions" Wiki guide needs additional explanation #6537 (comment), 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: Medium (because of Github Actions testing)
- Relationships: This ER (ER: Ensure 'reopened' PRs get checked for properly linked issues #8870) should be listed as the issue's parent
- Size: 0.5pt
- 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]
Metadata
Metadata
Assignees
Labels
Complexity: MediumEREmergent RequestEmergent RequestFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicReady for Prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Type
Projects
- StatusShow more project fieldsNew Issue Approval
Activity
[-]ER: [replace with info ][/-][+]ER: Ensure 'reopened' PRS get checked for properly linked issues[/+][-]ER: Ensure 'reopened' PRS get checked for properly linked issues[/-][+]ER: Ensure 'reopened' PRs get checked for properly linked issues[/+]daras-cu commentedon Nov 14, 2026
@meghan-oconnell thanks for writing this! A couple notes for your potential solutions: since it requires testing GitHub actions I think the issue should be a Medium, and probably size 0.5. Also under Relationships they'll want to put this ER as the parent issue. Otherwise this looks good to go!
meghan-oconnell commentedon Nov 17, 2026
Thank you @daras-cu! I have updated that!