Repository navigation
Epic: Create issues to populate github-handle variable in leadership teams #8428
Description
Overview
We need to create issues to populate the github-handle variable with the correct handle for each member of the leadership team. Eventually, this variable will replace the existing github and picture variables, reducing redundancy in the project data.
Good First Issues:
- Populate github-handle for Bonnie Wolfe in
tdm-calculator.md#8827 - Populate github-handle for John Darragh in
tdm-calculator.md#8828 - Populate github-handle for Parisa Jannatifard in
tdm-calculator.md#8829 - Populate github-handle for Nilakshi Sahai in
tdm-calculator.md#8830 - Populate github-handle for Heejung Hong in
tdm-calculator.md#8831 - Populate github-handle for Marlena Mellody Khim-Sai in
tdm-calculator.md#8832 - Populate github-handle for Melissa Perry in
tdm-calculator.md#8833 - Populate github-handle for Abby Rivard in
tdm-calculator.md#8834 - Populate github-handle for Karen Coronel in ballot-nav.md #8850
- Populate github-handle for Stacey Rebekah Scott in ballot-nav.md #8851
- Populate github-handle for Layne Mostyn in ballot-nav.md #8852
- Populate github-handle for Andrew Steman in ballot-nav.md #8853
- Populate github-handle for Zuri Smith in ballot-nav.md #8854
- Populate github-handle for Jon Lam in ballot-nav.md #8855
Action Items
- Create spreadsheet to list projects that have team members and keep track of issue creation - completed
- Create template for the population of the variable github-handle for a member of a leadership team 1
- Create issue to make GitHub template - Create issue template for GFIs that populate 'github-handle' variable #8461
- Create a new template using this example (Epic: Create issues to add github-handle to leadership teams #5441 (comment)), that will be an issue making issue to create each project file's issues, from the prior template. They will be level 1 issues and should have the
Issue Making: Level 1label- Create issue to make GitHub template
- Create the issue making issues for each project file and record issue on spreadsheet.2
For Merge Team
- When all the issues created from this epic are completed, check each project.md file to make sure that any new members that have been added also have the github-handle variable populated, and if not, make remaining issues and add them to this issue. - this step gets repeated until every project file has the variable populated for every team member.
Resources/Instructions
- Template of what a project file looks like: https://github.com/hackforla/website/wiki/project.md-file-template
- Template draft: Epic: Create issues to populate github-handle variable in leadership teams #8428 (comment)
Issues Templates
- Epic for project file: This IM1 issue will use the populate template to create an issue for leadership item
- Populate a single github-handle: This good first issue will populate the github-handle variable for a single project member
Footnotes
Metadata
Metadata
Assignees
Labels
See the Issue Making label to understand the issue writing difficulty levelHomepage Launch Countdown Could HaveTracking all issues related to homepage launchMaking a template + Create a Level 1 issue(s) + sample issue using templateA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)Tasks for back-end developersTasks for front end developersCan be done in 4-6 hoursNeeds to be worked on by a particular timeframe
Activity
xnealcarson commentedon Nov 25, 2025
Title: Populate github-handle for [INSERT NAME] in [INSERT PROJECT FILE]
Prerequisite
Overview
We need to populate the 'github-handle' variable with the correct GitHub username for each member of the leadership team. Eventually
github-handlewill replace thegithubandpicturevariables, reducing redundancy in the project file.Action Items
_projects/[PROJECT FILE]in the IDE 1githubvariable URL (https://github.com/githubusername)with
github-handle. YAML doesn't allow tabs; it requires spaces.For Merge Team
Resources/Instructions
https://github.com/hackforla/website/wiki/project.md-file-template
https://jekyllrb.com/
Project Webpage: https://www.hackforla.org/projects/[INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION]
Footnotes
https://github.com/hackforla/website/blob/gh-pages/_projects/[INSERT_PROJECT_FILE]?plain=1 ↩
daras-cu commentedon Nov 25, 2025
@ExperimentsInHonesty please see the template draft for the good first issues to add GitHub handles to project files
ExperimentsInHonesty commentedon Jan 6, 2026
Title: Populate github-handle for [INSERT NAME] in [INSERT PROJECT FILE]
Prerequisite
Overview
We need to populate the 'github-handle' variable with the correct GitHub username for each member of the leadership team. Eventually
github-handlewill replace thegithubandpicturevariables, reducing redundancy in the project file.Action Items
_projects/[PROJECT FILE]in the IDE 1githubvariable URL (e.g.,https://github.com/githubusername)with
For Merge Team
Resources/Instructions
Footnotes
https://github.com/hackforla/website/blob/gh-pages/_projects/[INSERT_PROJECT_FILE]?plain=1 ↩
18 remaining items
ExperimentsInHonesty commentedon Jun 2, 2026
@daras-cu @kdaca19xx @xnealcarson I am generally approving this template (see last comment). I think we should try to make one IM1 issue out of it to test it. If all goes well, we can make an issue to add the template to the to the repo. Use TDM Calculator as the test
HackforLABot commentedon Jun 29, 2026
yielderdev commentedon Oct 13, 2026
As @emoore36 indicated in this comment in issue #8829, the github handle variable is already populated for Parisa Jannatifard aka github handle: "Parisajf"
I'm going to check off the box for that issue in this Epic, add the ignore label to #8829 and close it for now @daras-cu . Hopefully that'll make the HackForLABot happy in this circumstance.
Actually, it turns out every other person besides Bonnie Wolfe and John Darragh has already been populated in
_projects/tdm-calculator.md. Will be seeking consult on how to proceed with the other issues.Update 10/14/26 after conferring with leadership:
All issues with an already-populated github handle will be labeled as "Ignore: No Longer a Problem" and closed (all but the first two #8827 and #8828 .
This epic being a testrun for populating these
github-handle:fields across_projects/, this is good info and there was discussion of adding templating to future project epics to account for already-populatedgithub-handle:fields.