Repository navigation
Create issues to populate 'github-handle' variables in Ballot Nav #8847
Description
Prerequisites
- 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.
- Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.
Overview
We need to create issues to populate the github-handle variable for each project team member in Ballot Nav with the correct GitHub handle.
github-handle will eventually replace the github and picture variables, reducing redundancy in the project file, but that will not be done in this issue.
Action Items
- For each team member listed in _projects/ballot-nav.md, find the
github-handlevariable. If this variable is not assigned a value, create an issue for the team member using the template - For each issue:
- In the title, replace [INSERT NAME] with the member's name
- In the title, replace [INSERT PROJECT FILE] with the project file name, e.g. 'website.md'
- Under Action Items, replace [INSERT MEMBER NAME] with the member's name (in 3 places)
- Under Action Items, replace [INSERT PROJECT FILE] with the project file name
- Under Action Items, replace the [INSERT GITHUB USERNAME] placeholder with the member's GitHub username (this may be found at the end of their
githubURL underlinks - Under Resources, replace [INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION] with the project name without the extension, e.g. 'website'
- 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"
- Add the Milestone "08. Team Workflow"
- When the issue has been created, add this issue as the parent issue under "Relationships"
- List the issue number in Epic: Create issues to populate github-handle variable in leadership teams #8428 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 (all project markdown files use this format)
- Project Webpage: https://www.hackforla.org/projects/ballot-nav (the public URL of the file you are editing)
- This issue is part of Epic: Create issues to populate github-handle variable in leadership teams #8428.
- https://jekyllrb.com/ (the whole site is built on Jekyll)
Metadata
Metadata
Assignees
Labels
See the Issue Making label to understand the issue writing difficulty levelMake issues from a template and a spreadsheetA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)Good for newcomersFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.needs a senior review either to do some re writing or to approve it for ready for prioritizationTasks for back-end developersTasks for front end developersCan be done in 3 hours or less
Activity
1 remaining item
daras-cu commentedon Oct 25, 2026
@KyleA99 I assigned you to this as I know you've been waiting for an IM 1 issue, if you'd prefer to work on something else feel free to unassign yourself.
KyleA99 commentedon Oct 25, 2026
Thank you @daras-cu !
KyleA99 commentedon Oct 27, 2026
This issue did not mention to do this, however, I did replace the
[INSERT_PROJECT_FILE]in the footnotes link. If I shouldnt have done this, let me know, and I'll revert this.sushma110396 commentedon Nov 1, 2026
@KyleA99 @daras-cu Merge team review completed. Verified that all six sub-issues have been created with the required information and are linked to the parent issue. The updated footnote links also look correct.
Closing this issue as the required issue-creation work is complete.