Skip to content

Fix edge-case bug in "Issue Trigger" workflow#8635

Open
t-will-gillis wants to merge 1 commit intohackforla:gh-pagesfrom
t-will-gillis:fix-bug-issue-trigger-8634
Open

Fix edge-case bug in "Issue Trigger" workflow#8635
t-will-gillis wants to merge 1 commit intohackforla:gh-pagesfrom
t-will-gillis:fix-bug-issue-trigger-8634

Conversation

@t-will-gillis
Copy link
Copy Markdown
Member

Fixes #8634

What changes did you make?

  • In preliminary-update-comment.js added filter to remove PRs

Why did you make the changes (we will use this info to test)?

  • We need to ensure that only issues are returned in the query so that if a dev assign themselves to their own PR, the results do not include it- this will cause GraphQL to return an error and the automation checks will fail.

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Screenshot 2024-10-28 154514

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

  • I have checked this PR for CodeQL alerts and none were found.
  • I found CodeQL alert(s), and (select one):
    • I have resolved the CodeQL alert(s) as noted
    • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
    • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)
Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied

image

Visuals after changes are applied

image

@github-actions github-actions Bot added Bug Something isn't working role: back end/devOps Tasks for back-end developers Complexity: Medium Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms labels May 10, 2026
@github-actions
Copy link
Copy Markdown

Want to review this pull request? Take a look at this documentation for a step by step guide!


From your project repository, check out a new branch and test the changes.

git checkout -b t-will-gillis-fix-bug-issue-trigger-8634 gh-pages
git pull https://github.com/t-will-gillis/website.git fix-bug-issue-trigger-8634

@github-actions github-actions Bot added the size: 5pt Can be done in 19-30 hours label May 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Complexity: Medium Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 5pt Can be done in 19-30 hours

Projects

Status: PR Needs review

Development

Successfully merging this pull request may close these issues.

Fix bug in "Issue Trigger" causing an edge-case failure at the dev multi-issue assignment check

1 participant