-
-
Notifications
You must be signed in to change notification settings - Fork 843
Open
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelIssue Making: Level 3Making a template + Create a Level 1 issue(s) + sample issue using templateMaking a template + Create a Level 1 issue(s) + sample issue using templateP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 1ptCan be done in 4-6 hoursCan be done in 4-6 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
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.
Action Items
- Create template for the population of the variable github-handle for a member of a leadership team 1
- Create issue to make GitHub template (see Epic: Create issues to populate github-handle variable in leadership teams #8428 (comment))
- 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 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
https://github.com/hackforla/website/wiki/project.md-file-template
Footnotes
Metadata
Metadata
Assignees
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelIssue Making: Level 3Making a template + Create a Level 1 issue(s) + sample issue using templateMaking a template + Create a Level 1 issue(s) + sample issue using templateP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 1ptCan be done in 4-6 hoursCan be done in 4-6 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Type
Projects
Status
ERs and epics that are ready to be turned into issues