Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
11 tasks done
Tracked by #5441
roslynwythe opened this issue Jul 31, 2024 · 9 comments
Closed
11 tasks done
Tracked by #5441
Assignees
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet 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

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Jul 31, 2024

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 Epic: Create issues to add github-handle to leadership teams #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

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jul 31, 2024

This comment was marked as outdated.

@roslynwythe roslynwythe added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers epic size: 0.25pt Can be done in 0.5 to 1.5 hours Issue Making: Level 1 Make issues from a template and a spreadsheet Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Ready for Prioritization P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jul 31, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the x. Technical debt milestone Aug 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Aug 5, 2024
@FamousHero FamousHero self-assigned this Sep 10, 2024
@HackforLABot

This comment was marked as outdated.

@HackforLABot HackforLABot added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Sep 10, 2024
@HackforLABot HackforLABot moved this from ERs and epics that are ready to be turned into issues to New Issue Approval in P: HfLA Website: Project Board Sep 10, 2024
@mchait18 mchait18 self-assigned this Nov 28, 2024
@mchait18 mchait18 moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board Nov 28, 2024
@HackforLABot
Copy link
Contributor

HackforLABot commented Nov 28, 2024

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
Copy link
Member

mchait18 commented Nov 29, 2024

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

@mchait18 mchait18 moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Board Nov 29, 2024
@mchait18 mchait18 added the ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization label Nov 29, 2024
@siyunfeng
Copy link
Member

@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
Copy link
Member

mchait18 commented Dec 3, 2024

@t-will-gillis t-will-gillis removed the ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization label Dec 9, 2024
@t-will-gillis
Copy link
Member

t-will-gillis commented Dec 9, 2024

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

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

@mchait18
Copy link
Member

mchait18 commented Dec 9, 2024

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

@t-will-gillis t-will-gillis added ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization and removed ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels Dec 9, 2024
@t-will-gillis
Copy link
Member

Thanks @mchait18! Closing this as successfully completed.

@github-project-automation github-project-automation bot moved this from Questions / In Review to QA in P: HfLA Website: Project Board Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet 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
Development

No branches or pull requests

7 participants