-
-
Notifications
You must be signed in to change notification settings - Fork 843
[Home Unite Us] updated Tyler Thome's role #8150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Home Unite Us] updated Tyler Thome's role #8150
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. |
|
Availability: Weekdays After 7 pm |
sandavid11
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @caz002, thank you for taking on this issue.
Things done well
- PR was made from the correct branch
- Linked issue included
- Included before and after images
- No changes were made other than requested in the issue
Great job! I approved PR. Thank you!
rogerioduenas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @caz002
Great job with this pull request!
- The branching was done correctly.
- Issue number was listed.
- The PR title is descriptive of the changes.
- Changes were made correctly in the code.
- Changes appear correctly on the site - Tyler Thome's position at HUU was changed from Tech Lead to Lead Developer.
- Relevant images were included to show visual changes.
- The PR request clearly states what was updated.
Again, great work and thanks for taking the time to contribute to the website!
|
Availability: Monday - Friday, 10:00 AM to 4:00 PM JST |
|
Nice one! Thanks for working on this. I have verified the changes are accurate and will now merge. |
… Developer
Fixes #7957
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)
Visuals before changes are applied
Visuals after changes are applied