Skip to content

Fixed Name Inconsistency in tech-work-experience.md file#8647

Open
emoore36 wants to merge 1 commit into
hackforla:gh-pagesfrom
emoore36:fix-name-tech-exp-file-8574
Open

Fixed Name Inconsistency in tech-work-experience.md file#8647
emoore36 wants to merge 1 commit into
hackforla:gh-pagesfrom
emoore36:fix-name-tech-exp-file-8574

Conversation

@emoore36
Copy link
Copy Markdown
Member

@emoore36 emoore36 commented May 19, 2026

Fixes #8574

What changes did you make?

  • changed "Google Data" to "Looker"

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

  • to keep the Languages/Technologies/Tools information 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

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
Projects Page - Before Image
Tech Experience Page - Before Image
Visuals after changes are applied
Projects Page - After image
Tech Experience Page - After image

@github-actions github-actions Bot added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less Draft Issue is still in the process of being created p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels May 19, 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 emoore36-fix-name-tech-exp-file-8574 gh-pages
git pull https://github.com/emoore36/website.git fix-name-tech-exp-file-8574

@emoore36 emoore36 removed the Draft Issue is still in the process of being created label May 19, 2026
@castillios castillios self-requested a review May 19, 2026 23:59
@castillios
Copy link
Copy Markdown
Member

castillios commented May 20, 2026

Review ETA: 5/19 by EOD
Availability: Weekdays before 7PM

Copy link
Copy Markdown
Member

@castillios castillios left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 Studio with Looker 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!

@emoore36 emoore36 requested a review from castillios May 20, 2026 05:13
@sushma110396 sushma110396 self-requested a review May 20, 2026 21:21
@sushma110396
Copy link
Copy Markdown
Member

Review ETA: 2 PM 05/20/26
Availability: Weekdays after 6PM PST

Copy link
Copy Markdown
Member

@sushma110396 sushma110396 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@github-project-automation github-project-automation Bot moved this from PR Needs review to PRs ✅ waiting for merge team in P: HfLA Website: Project Board May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

good first issue Good for newcomers p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Projects

Status: PRs ✅ waiting for merge team

Development

Successfully merging this pull request may close these issues.

Fix Name Inconsistency in tech-work-experience.md file

3 participants