Skip to content

Conversation

@valdezg
Copy link
Member

@valdezg valdezg commented Apr 5, 2025

Fixes #7879

What changes did you make?

  • Added Trillium Smith / changed to lead developer
  • updated picture
  • updated github handle

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

  • To work on my first issue
  • change profile picture
  • change role name from developer to lead developer

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

image

Visuals after changes are applied

image

@github-actions
Copy link

github-actions bot commented Apr 5, 2025

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 valdezg-update-trillium-7879 gh-pages
git pull https://github.com/valdezg/website.git update-trillium-7879

@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 size: 0.25pt Can be done in 0.5 to 1.5 hours labels Apr 5, 2025
@DrAcula27 DrAcula27 self-requested a review April 7, 2025 22:11
Copy link
Member

@DrAcula27 DrAcula27 left a comment

Choose a reason for hiding this comment

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

Hi @valdezg,
Great start on your Good First Issue!

What you did well:

  • Fixed and linked to the correct issue #7879
  • Succinctly answered the questions at the top of the PR.
  • Correctly replaced the text within the _projects/vrms.md file.

What needs work:

  • In the CodeQL Alerts section of the PR:
    • Please check the relevant checkbox(s) answering whether you got any CodeQL alerts when you made the PR.
  • In the Screenshots of Proposed Changes To The Website section of the PR:
    • Please follow the instructions in the Notes comment to add a picture of the before and after changes to the website. If there were no visual changes, please delete the script and add 'No visual changes to the website'.
  • In the next website meeting, please bring up why you had to add the vrms.md file. If this was necessary, and I am missing the reason, feel free to let me know!

Great job so far, you got this!

@github-project-automation github-project-automation bot moved this from PR Needs review to PRs being reviewed in P: HfLA Website: Project Board Apr 7, 2025
@daras-cu daras-cu requested a review from kdaca19xx April 9, 2025 02:35
@kdaca19xx
Copy link
Member

Review ETA: 6 PM 4/12/2025
Availability: after 12noon Saturday

@katiejnete
Copy link
Member

Review ETA: EOD 4/9/25
Availability: Wednesday Nights

Copy link
Member

@katiejnete katiejnete left a comment

Choose a reason for hiding this comment

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

Hi @valdezg , good job on your first GFI. Thank you for taking on this issue.

Things you did well:

  • PR is done with the correct branch.
  • PR contains correctly formatted linked issue.
  • PR follows correct format and is properly written.
  • The changes are applicable to the issue.
  • Website is still user-friendly and links and components still work as intended.

Suggested changes:

  • Please check the proper CodeQL Alerts checkbox.
  • Please make sure the before and after screenshots are appropriately included. Please remove what you have, drag/drop images, and wait for them to properly render.
  • You have created a duplicate file in the root website directory vrms.md. Please delete this file.

Notes:

  • Your issue branch name could include more detail update-project-profile-trillium-smith-7879. No need to change it for this issue.

After making these changes, re-request a review from me. Thank you for your hard work!

valdezg added 2 commits April 9, 2025 20:12
deleting manual file change
deleting duplicate branch
Copy link
Member Author

@valdezg valdezg left a comment

Choose a reason for hiding this comment

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

deleting duplicate branch

@valdezg
Copy link
Member Author

valdezg commented Apr 10, 2025

Added before and after pictures in comment. I also deleted a branch that was a duplicate and removed a file that I accidentaly added by mistake. Please let me know if this is ok for now. Thanks everyone!

@valdezg valdezg requested review from DrAcula27 and katiejnete April 10, 2025 03:29
@katiejnete
Copy link
Member

Hi @valdezg , the wrong file was deleted. Please keep the file vrms.md in the_projects directory but remove the vrms.md file from the root directory, website. For the CodeQL Alerts checkboxes, the first checkbox will suffice since none were found.

After making these changes, re-request a review from me. Thank you for your hard work!

Copy link
Member Author

@valdezg valdezg left a comment

Choose a reason for hiding this comment

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

need to restore this file

@valdezg
Copy link
Member Author

valdezg commented Apr 10, 2025

hi @katiejnete I tried removing one of the branches but I am not sure how to restore the file after deleting it. Is there anyway to do this without re doing the entire commit? Sorry for the confusion.

@katiejnete
Copy link
Member

Hi @valdezg , you can try this git revert <oldest_commit_hash>^..<latest_commit_hash> (git revert abc123^..def456 ). It's inclusive, and you may or may not have to resolve merge conflicts. After reverting, you can push like normal.

Copy link
Member

@kdaca19xx kdaca19xx left a comment

Choose a reason for hiding this comment

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

Strong effort, Valdezg!

Things Done Well

  • The pull request was done with the correct branch.
  • There is a linked issue.
  • I understood the linked issue.
  • I'm stating the obvious by now, but I couldn't look at the file in the Files changed tab (or on valdezg's branch in VS Code), and I couldn't view changes in the browser via Docker Desktop (Screenshots taken).

Suggestions

  • Please see what others advised in the comments above.

@valdezg
Copy link
Member Author

valdezg commented Apr 11, 2025

Okay thanks everyone for taking a look. I basically had to go back and redo everything. I used git revert and was able to restore the missing file since I accidentally deleted it on githubs website. Please let me know if the branch looks better now and I am adding through the correct method.

@valdezg valdezg requested a review from kdaca19xx April 11, 2025 04:51
Copy link
Member

@DrAcula27 DrAcula27 left a comment

Choose a reason for hiding this comment

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

@valdezg Much better! This looks good to me now. Approved 👍

Copy link
Member

@katiejnete katiejnete left a comment

Choose a reason for hiding this comment

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

Thank you for your hard work @valdezg , I approve this PR.

@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 Apr 12, 2025
@kdaca19xx
Copy link
Member

Thx for making those changes, @valdezg. Approved!

@mugdhchauhan
Copy link
Member

Nice one @valdezg! Thank you for working on this and making the changes requested by the reviewers.

For the PR title, please could you remove the issue number and make it more descriptive such as Update Project Profile: VRMS New GitHub handle and role of Trillium Smith. Thanks.

@mugdhchauhan
Copy link
Member

Hey @kdaca19xx, thank you for re-reviewing.

Please review by going to the "Files changed" tab, clicking on the green "Review changes" button, completing the appropriate sections, and finally pressing the "Submit review" button. The screenshot below may be helpful.

Screenshot

Screenshot

Feel free to reach out to me if you need help with anything. Thank you for working on this.

@valdezg valdezg changed the title Update trillium 7879 Update Project Profile: VRMS New GitHub handle and role of Trillium Smith Apr 15, 2025
@valdezg
Copy link
Member Author

valdezg commented Apr 15, 2025

Hi @mugdhchauhan. I just updated the title of the PR! Thanks let me know if you need any more changes. Best

Copy link
Member

@kdaca19xx kdaca19xx left a comment

Choose a reason for hiding this comment

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

Approved!

@daras-cu daras-cu merged commit 7fd1651 into hackforla:gh-pages Apr 16, 2025
5 checks passed
@valdezg valdezg deleted the update-trillium-7879 branch May 18, 2025 04:56
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 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: VRMS updated Github Handle and Role of Trillium Smith

6 participants