Skip to content

Conversation

@bragelbytes
Copy link
Member

@bragelbytes bragelbytes commented Nov 15, 2025

Fixes #7802

What changes did you make?

  • Added "github-handle" variable to Seymour Liao in Lucky Parking Project team.

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

Each person in the list requires this variable so I updated it to be consistent with guidelines.
Eventually, github-handle will replace the github and picture variables to reduce redundancy.

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.

Changes are free from CodeQL 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)

No visual changes.

@github-actions
Copy link

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 bragelbytes-add-github-handle-variable-7802 gh-pages
git pull https://github.com/bragelbytes/website.git add-github-handle-variable-7802

@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 P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) size: 0.25pt Can be done in 0.5 to 1.5 hours labels Nov 15, 2025
@izzy-me
Copy link
Member

izzy-me commented Nov 15, 2025

ETA: 11/14 at 6:20 pm
Availability: 11/14 from 6-7pm

@izzy-me izzy-me requested a review from Jaretzbalba November 15, 2025 02:23
@izzy-me izzy-me requested review from izzy-me and removed request for Jaretzbalba November 15, 2025 02:23
Copy link
Member

@izzy-me izzy-me left a comment

Choose a reason for hiding this comment

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

Hi @bragelbytes!

Great work here. Two minor edits:

  1. Make sure to fill out the CodeQL Alerts as part of the pull request. It looks like you don't have any so it should be good to go. Just make sure to mark that your changes are free of alerts.
  2. Try to be slightly more descriptive with question 2, i.e. you can say that each person listed requires this new variable so you are updating the file to be consistent with these guidelines.

Otherwise, great work! Once those minor edits are made, I can approve the PR.

  • PR contains correct branch
  • linked issue properly added
  • source code changes are applicable and clean

@github-project-automation github-project-automation bot moved this from PR Needs review to PRs being reviewed in P: HfLA Website: Project Board Nov 15, 2025
@bragelbytes bragelbytes requested a review from izzy-me November 16, 2025 21:00
@santiseccovidal
Copy link
Member

ETA: 11/17 at 6:00 pm
Availability: 11/17 from 5-7pm

Copy link
Member

@izzy-me izzy-me left a comment

Choose a reason for hiding this comment

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

Looks great! Thanks for making the requested changes. PR approved.

Copy link
Member

@santiseccovidal santiseccovidal left a comment

Choose a reason for hiding this comment

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

Hi @bragelbytes good work with the code changes. Question 1 "What changes..." is alright but the second sentence is more geared towards Question 2 "Why...". Question 2 needs another answer, check out this PR and try to work on it #8419
Thanks for working on this

Copy link
Member

@santiseccovidal santiseccovidal left a comment

Choose a reason for hiding this comment

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

Hi @bragelbytes well done, now the What and Why sections are more clear.

@github-project-automation github-project-automation bot moved this from PRs being reviewed to PRs ✅ waiting for merge team in P: HfLA Website: Project Board Nov 21, 2025
Copy link
Member

@izzy-me izzy-me left a comment

Choose a reason for hiding this comment

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

Great work!

@DDVVPP
Copy link
Member

DDVVPP commented Nov 21, 2025

Hi @bragelbytes! Thanks for working on this issue - Just wanted to leave a comment to remind you to check of the completed items in the Action Items checklist in the issue. Thanks again!

@xnealcarson xnealcarson merged commit c8cb74b into hackforla:gh-pages Nov 22, 2025
18 of 19 checks passed
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: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Projects

Development

Successfully merging this pull request may close these issues.

Add github-handle for Seymour Liao in lucky-parking.md

5 participants