Skip to content

added docker technologies to lucky-parking project - #8764

Merged
castillios merged 1 commit into
hackforla:gh-pagesfrom
edwlope:update-lucky-parking-8655
Sep 3, 2026
Merged

added docker technologies to lucky-parking project#8764
castillios merged 1 commit into
hackforla:gh-pagesfrom
edwlope:update-lucky-parking-8655

Conversation

@edwlope

@edwlope edwlope commented Aug 31, 2026

Copy link
Copy Markdown
Member

Please note: You must be a member of the HFLA website team in order to create pull requests. Please see our page on how to join us as a member at HFLA: https://www.hackforla.org/getting-started. Delete this message if you joined this team via onboarding.

Fixes #8655

What changes did you make?

  • Added 'Docker' under technologies

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

  • In order to keep project 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 lucky-parking-before
Visuals after changes are applied lucky-parking-after

@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 edwlope-update-lucky-parking-8655 gh-pages
git pull https://github.com/edwlope/website.git update-lucky-parking-8655

@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) time sensitive Needs to be worked on by a particular timeframe P-Feature: Projects page https://www.hackforla.org/projects/ size: 0.25pt Can be done in 0.5 to 1.5 hours HLC: M Homepage Launch Countdown Must Have labels Aug 31, 2026
@computarisis
computarisis self-requested a review September 1, 2026 13:22
@computarisis

Copy link
Copy Markdown
Member

ETA: Wed, Sep 2 by 8: 00PM ET
Availability: Daily after 8 PM ET

@jjam02 jjam02 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Correct

  • Named the branch correctly
  • Made the correct changes in the right file
  • Visual changes show up as they should

Needs Changes

  • mark all the action items on the original issue
  • Mark the correct checkbox for the CodeQL section of the pull request

Avail: W/Th/F 1pm-3pm PST

@github-project-automation github-project-automation Bot moved this from PR Needs review to PRs being reviewed in P: HfLA Website: Project Board Sep 1, 2026

@computarisis computarisis left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hi @edwlope! I concur with @jjam02 in the need for checking off the missing instruction items. Other than that, your branch was created correctly, and I was able to validate the changes locally; good job on tackling the issue!

@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 Sep 3, 2026
@castillios

Copy link
Copy Markdown
Member

Great work @edwlope! One small formatting nit: don't forget to remove the small note at the beginning of the PR template so that your final PR starts with "Fixes #8655".

Merging in your PR now!

@castillios
castillios merged commit d105ef8 into hackforla:gh-pages Sep 3, 2026
18 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 HLC: M Homepage Launch Countdown Must Have P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) P-Feature: Projects page https://www.hackforla.org/projects/ 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 time sensitive Needs to be worked on by a particular timeframe

Projects

Development

Successfully merging this pull request may close these issues.

Update Project Profile: Lucky Parking (Add Tech: Docker)

4 participants