Fixed Name Inconsistency in tech-work-experience.md file#8647
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: 5/19 by EOD |
There was a problem hiding this comment.
Hi emoore36! Ran locally and confirmed your changes, everything looks great. The image screenshots included are very organized as well.
Done correctly
- Replaced
Google Data StudiowithLooker Studio - PR completed in correct branch
- Issue is correctly linked
- Issue action items have been checked off and project status has been set
- Correctly assigned yourself and included your availability in the issue
- Screenshots of visual changes included
Suggested changes
- Ensure CodeQL alert boxes are checked off
Otherwise everything has been done well! Before I approve, just apply that one small change then re-request a review from me. Thank you for your contribution!
|
Review ETA: 2 PM 05/20/26 |
sushma110396
left a comment
There was a problem hiding this comment.
I have verified the changes locally. Looks good to me!
All the required steps have been followed correctly.
- Pull request has the correct branch name
- There is a linked issue
- File change is correct.
- Visual changes look good.
PR approved.
Fixes #8574
What changes did you make?
Why did you make the changes (we will use this info to test)?
Languages/Technologies/Toolsinformation up-to-date.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
Projects Page - Before
Tech Experience Page - Before
Visuals after changes are applied
Projects Page - After
Tech Experience Page - After