Skip to content

Create workflow to check linked PR#2

Closed
myronchen-git wants to merge 4 commits intogh-pagesfrom
check-closed-issue-for-linked-pr-8139
Closed

Create workflow to check linked PR#2
myronchen-git wants to merge 4 commits intogh-pagesfrom
check-closed-issue-for-linked-pr-8139

Conversation

@myronchen-git
Copy link
Owner

Please note: You must be a member of the HFLA website team in order to create pull requests. Please see our page on how to join us as a member at HFLA: https://www.hackforla.org/getting-started. Delete this message if you joined this team via onboarding.

Fixes #1

What changes did you make?

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

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

@myronchen-git myronchen-git linked an issue Nov 20, 2025 that may be closed by this pull request
@myronchen-git myronchen-git force-pushed the check-closed-issue-for-linked-pr-8139 branch 2 times, most recently from 8f7f49b to 9460749 Compare November 21, 2025 03:13
@myronchen-git myronchen-git removed a link to an issue Nov 21, 2025
@myronchen-git myronchen-git force-pushed the check-closed-issue-for-linked-pr-8139 branch 19 times, most recently from 863a19f to f6e14f7 Compare November 24, 2025 23:13
@myronchen-git myronchen-git linked an issue Nov 24, 2025 that may be closed by this pull request
@myronchen-git myronchen-git removed a link to an issue Nov 24, 2025
@myronchen-git myronchen-git force-pushed the check-closed-issue-for-linked-pr-8139 branch 5 times, most recently from c25e3ad to 00daeee Compare November 27, 2025 00:59
@myronchen-git myronchen-git linked an issue Nov 27, 2025 that may be closed by this pull request
@myronchen-git myronchen-git force-pushed the check-closed-issue-for-linked-pr-8139 branch from 00daeee to 4b1d399 Compare November 27, 2025 01:15
@myronchen-git myronchen-git force-pushed the check-closed-issue-for-linked-pr-8139 branch from 64e8558 to ee6c177 Compare January 17, 2026 16:41
@myronchen-git myronchen-git removed a link to an issue Jan 17, 2026
@myronchen-git myronchen-git linked an issue Jan 17, 2026 that may be closed by this pull request
@myronchen-git myronchen-git removed a link to an issue Jan 17, 2026
@myronchen-git myronchen-git force-pushed the check-closed-issue-for-linked-pr-8139 branch from 7646a1d to bbd685a Compare February 5, 2026 21:38
@myronchen-git myronchen-git deleted the check-closed-issue-for-linked-pr-8139 branch February 6, 2026 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant