Skip to content

Create issues to populate 'github-handle' variables in TDM Calculator #8807

Closed
6 of 8 issues completed
Closed

Description

@daras-cu

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

We need to create issues to populate the github-handle variable for each project team member in tdm-calculator.md 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/tdm-calculator.md, create an issue 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 github URL under links
    • 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"
    • 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

Activity

  1. added this to the 08. Team workflow milestone on Sep 26, 2026
  2. added
    P-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
    size: 0.5ptCan be done in 3 hours or less
    Issue Making: Level 1Make issues from a template and a spreadsheet
    Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty level
    on Sep 26, 2026
  3. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Sep 26, 2026
  4. added and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Sep 29, 2026
  5. 10 remaining items

  6. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Oct 10, 2026
  7. moved this from Questions / In Review to In progress (actively working) in P: HfLA Website: Project Boardon Oct 10, 2026
  8. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Oct 10, 2026
  9. yielderdev commented on Oct 14, 2026

    @yielderdev
    Member

    Just noting here that for all but the first two issues (#8827 and #8828) I've replaced the label 'ready for merge team with 'Ignore: no longer a problem' to satisfy the HFLA Bot and closed them.

    Thanks for your work and vigilance @emoore36 .

  10. added
    non-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.
    and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Oct 16, 2026
  11. moved this from Questions / In Review to QA in P: HfLA Website: Project Boardon Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelIssue Making: Level 1Make issues from a template and a spreadsheetP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicgood first issueGood for newcomersnon-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.role: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.5ptCan be done in 3 hours or less

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions