Skip to content

Added Kerstin Carson to website project pg#8527

Merged
t-will-gillis merged 1 commit intohackforla:gh-pagesfrom
mocodesss:add-kerstin-carson-prject-profile-8440
Feb 27, 2026
Merged

Added Kerstin Carson to website project pg#8527
t-will-gillis merged 1 commit intohackforla:gh-pagesfrom
mocodesss:add-kerstin-carson-prject-profile-8440

Conversation

@mocodesss
Copy link
Member

@mocodesss mocodesss commented Feb 24, 2026

Fixes #8440

What changes did you make?

  • added this to _projects/website.md:
- name: Kerstin Carson
   github-handle: kdaca19xx
   role: Merge Team
   links:
     slack: https://hackforla.slack.com/team/U08G2GETURJ
     github: https://github.com/kdaca19xx
   picture: https://avatars.githubusercontent.com/kdaca19xx

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

  • Kerstin Carson is now a member of the Merge Team so the list of project leadership needs to be updated.

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 before8440
Visuals after changes are applied after8440

@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 mocodesss-add-kerstin-carson-prject-profile-8440 gh-pages
git pull https://github.com/mocodesss/website.git add-kerstin-carson-prject-profile-8440

@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 Feb 24, 2026
@Mykola-Lopushenko Mykola-Lopushenko self-assigned this Feb 25, 2026
@Mykola-Lopushenko
Copy link
Member

Review ETA: 7 PM 02/25/26
Availability: 5-8 PM Wednesday-Saturday

Copy link
Member

@Mykola-Lopushenko Mykola-Lopushenko left a comment

Choose a reason for hiding this comment

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

Hi @mocodesss,
Great job!


Done Correctly

  • The merge from and to branches have been correctly set.
  • The issue has been correctly linked.
  • In the issue, you've correctly assigned yourself.
  • The CodeQL alerts have been correctly checked off.
  • In the issue, you've correctly set the project status.
  • In the issue, action items have correctly been checked off.
  • Visuals before/after changes are applied.

I approve your first issue.

Copy link
Member

@myronchen-git myronchen-git 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 completing this good first issue. Other than the one thing that needs to be changed, everything else is good. Good job.


Done Correctly

  • The merge from and to branches have been correctly set.
  • The issue has been correctly linked.
  • The pull request title is named properly.
  • The what in the pull request description is adequately described.
  • The CodeQL alerts have been correctly checked off.
  • Code changes have been correctly made.
  • In the originating issue, you've correctly assigned yourself.
  • In the originating issue, you've correctly set the project status.
  • In the originating issue, action items have correctly been checked off.
  • In the originating issue, you've given your availability and ETA.

Changes that need to be made

  • The why description in your pull request could be better. What you currently have reiterates the what. The why would need to explain why Kerstin needs to be added.

On a side note, in your originating issue 8440, you do not need to put before and after screenshots there. It is only needed in the pull request.

@github-project-automation github-project-automation bot moved this from PR Needs review to PRs being reviewed in P: HfLA Website: Project Board Feb 26, 2026
@myronchen-git
Copy link
Member

By the way, you shouldn't assign anybody as assignee for pull requests. I've went ahead and unassigned you already.

@mocodesss
Copy link
Member Author

Thank you @myronchen-git! That makes a lot of sense, I updated the "Why" to be more descriptive and looking at the big picture here. And, noted on no assignees, thank you for removing that.

Copy link
Member

@myronchen-git myronchen-git 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 making the changes. That's all from me. Good job.

@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 Feb 27, 2026
@t-will-gillis t-will-gillis merged commit 651ffe3 into hackforla:gh-pages Feb 27, 2026
17 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 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: Hackforla.org Website Add Kerstin Carson

4 participants