Adds "github-handle" to Jacob Zwang's section. - #8735
Conversation
|
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. |
|
Review ETA: 8 PM 8/14/26 |
Tomomi-K1
left a comment
There was a problem hiding this comment.
Great job @cchrizzle ! Confirmed project webpage is unchanged with this change applied!
✅ pull request is done with correct branch
✅ there is a linked issue
|
@KyleA99 can you please let us know your ETA for your review on this PR? |
|
Review ETA: 9 PM 8/18/26 |
Sorry forgot I was assigned to this one, will review shortly. |
|
@cchrizzle sorry about the delay on this review. Your work looks great.
|
|
Hi @cchrizzle, great work! Changes look great, I'm merging your PR in now. Just one note, please be sure to include a more detailed "why" in your description for future PRs. Thanks for your contributions! |
|
@castillios Got it will do, thank you! |
Fixes #7765
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
Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.
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)