Add github-handle for Selena Jiang in ems-triage-tracker.md

[dcotelessa]

Fixes #6723

What changes did you make?

• On _projects/ems-triage-tracker.md,
  • added github-handle: under - name: Selena Jiang

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

• We need to create a single variable github-handle to hold the github handle for Selena Jiang.
• No visual changes, but handle is now in the yaml.

No visual changes to website.

[github-actions]

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 dcotelessa-github-handle-selena-jiang-6723 gh-pages
git pull https://github.com/dcotelessa/website-hackforla.git github-handle-selena-jiang-6723

[mrodz]

Review ETA: 11 AM 5/26/24

This looks great! Besides the formatting issues presented by @t-will-gillis, you followed the items on the checklist and followed the protocol for submitting a PR.

• Branching done correctly
• Issue included
• Used spaces and correctly added the github-handle property
• Proper naming of the issue

Congrats on the PR! Thank you for the contribution.

[t-will-gillis]

Hey @dcotelessa Congrats on your first HfLA PR-

• Branches 'from' and 'into' are correct
• Original issue is linked
• A brief description of what was done and why is provided
• The code edit is clean

Some notes:

• Under the 'what change' and 'why', please remove the extra lines
• Under 'Screenshots of Proposed Changes..." please remove everything and replace with something to the effect of "No visual changes to website"

Thanks for working on this!

[t-will-gillis]

Hi @mrodz
There is not a specific format that needs to be followed when leaving a PR review, but there are specific items that a good PR review checks for, and it is helpful for everyone when the reviewer leaves specific (and encouraging) reasons for why the PR is being approved or why changes are being requested.

Here is an example of a well-done review: #6887 (review) When we look at this, we can see both that the reviewer has done a thorough job checking the PR, and the reviewee has done their job in creating the PR.

[mrodz]

Hi @mrodz There is not a specific format that needs to be followed when leaving a PR review, but there are specific items that a good PR review checks for, and it is helpful for everyone when the reviewer leaves specific (and encouraging) reasons for why the PR is being approved or why changes are being requested.

Here is an example of a well-done review: #6887 (review) When we look at this, we can see both that the reviewer has done a thorough job checking the PR, and the reviewee has done their job in creating the PR.

Thank you for the help! I am new to reviewing PR's and I appreciate the feedback. I will use your tips for the next PR's I review.

[dcotelessa]

Great feedback. I will keep the format in mind for readability. Thanks!

[t-will-gillis]

Hey @dcotelessa - Perfect, thanks for making the edits. Everything looks great!

[mrodz]

I am re-approving this PR as the formatting was fixed. Good work!