Create Issues to add new variable github-handle for members in not-today.md

[roslynwythe]

Prerequisites

1. You must be a member of Hack for LA to work on an issue. If you have not joined yet, please follow the steps on our Getting Started page.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As developers we need to create issues to update each project team member in not-today.md with a the new github-handle variable, that will eventually replace the github and picture variables, reducing redundancy in the project file.

Action Items

• [ ] For each team member listed in _projects/not-today.md that does not have a variable github-handle, create an issue using the template
• [ ] For each issue:
  • [ ] In the title, replace [INSERT MEMBER NAME] with the member's name
  • [ ] In the title, replace [INSERT PROJECT FILE] with not-today.md
  • [ ] Under Action Items, replace [INSERT MEMBER NAME] with the member's name (in 2 places)
  • [ ] Under Action Items, replace [INSERT PROJECT FILE] with not-today.md
  • [ ] Under Resources, replace [INSERT-PROJECT-FILE] with not-today.md
  • [ ] Under Resources, replace [INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION] with not-today
  • [ ] Apply the following labels: "ready for merge team", "good first issue", "role: front end", "role: back end/devOps", "size: 0.25pt", "P-Feature: Project Info and Page"
  • [ ] List the issue number in #5441 under Good First Issues
• [ ] When all issues have been created and listed, move this issue to the "Questions/In Review" column of the Project Board, and apply the label "ready for merge team"

Resources/Instructions

https://github.com/hackforla/website/wiki/project.md-file-template https://jekyllrb.com/ Webpage: https://www.hackforla.org/projects/not-today

• This issue is part of #5441

[github-actions[bot]]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[HackforLABot]

Hello @FamousHero, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

[HackforLABot]

Hi @mchait18, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: M-Th 9:30-3:30 EST ii. ETA: 12/2/2024 12 PM EST

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[mchait18]

The instruction says - Apply the following labels: "ready for merge team", "good first issue", "role: front end", "role: back end/devOps", "size: 0.25pt", "P-Feature: Project Info and Page". I see that the issue automatically has the label "ready for dev lead". Should I remove this label when I apply "ready for merge team" or include both?

Thank you Roslyn for your answer - resolved

[siyunfeng]

@mchait18 Please provide the issue number you created based on this Epic in the comment so the merge team can review and process it. You will need to include this Epic in the issues you created if you haven't.

[mchait18]

Thanks @siyunfeng. The issues I created based on this Epic are:

• #7781 and
• #7782.

[t-will-gillis]

Hi @mchait18 - Everything looks great! As @siyunfeng mentioned, for each of the two issues, please add a bullet point at the end of the "Resources/ Instructions" saying something like:

- This issue initiated by #7161

Also- I made a small edit in your comment above by putting each issue on its own line with a bullet point. This lets the full issue name get displayed, for example:

Without the bullet point #7161

• With the bullet point #7161

When you are through, let me know and I will close this issue.

[mchait18]

Thank you, @t-will-gillis. I corrected what you suggested.

[t-will-gillis]

Thanks @mchait18! Closing this as successfully completed.