Skip to content

ER: Ensure 'reopened' PRs get checked for properly linked issues #8870

Open

Description

@meghan-oconnell

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

@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

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]

Activity

  1. added
    Complexity: SmallTake this type of issues after the successful merge of your second good first issue
    on Nov 11, 2026
  2. changed the title [-]ER: [replace with info ][/-] [+]ER: Ensure 'reopened' PRS get checked for properly linked issues[/+] on Nov 11, 2026
  3. changed the title [-]ER: Ensure 'reopened' PRS get checked for properly linked issues[/-] [+]ER: Ensure 'reopened' PRs get checked for properly linked issues[/+] on Nov 11, 2026
  4. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Complexity: SmallTake this type of issues after the successful merge of your second good first issueEREmergent RequestFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsIssue Making: Level 2Make issue(s) from an ER or Epicready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: back end/devOpsTasks for back-end developerssize: 0.25ptCan be done in 0.5 to 1.5 hours

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions