Repository navigation
Open
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueP-Feature: Projects pagehttps://www.hackforla.org/projects/https://www.hackforla.org/projects/role: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hours
Milestone
Description
Prerequisite
- Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
- Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.
Overview
We need to update the 'Issue Making Populate github-handle' template so that the instructions for creating issues using the 'Populate github-handle' template are accurate.
Action Items
- Open the .github/ISSUE_TEMPLATE/issue-making-populate-github-handle-for-project.md file.
- Delete the following line directly below the file front matter:
## Title: Create issues to populate github-handle variable for members in [INSERT-PATH-TO-PROJECT-FILE]
- Under Action Items, replace the following line:
- [ ] For each team member listed in [INSERT PATH TO PROJECT FILE], create an issue using the [template](https://github.com/hackforla/website/issues/new?template=populate-github-handle.md)
with
- [ ] For each team member listed in [INSERT PATH TO PROJECT FILE], find the `github-handle` variable. If this variable is not assigned a value, create an issue for the team member using the [template](https://github.com/hackforla/website/issues/new?template=populate-github-handle.md)
- Under Action Items, replace the following line:
- Please note, you do not have to replace the [INSERT GITHUB USERNAME] placeholder
with
- [ ] 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`
- Directly after the action item
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 following action item:
- [ ] Add the Milestone "08. Team Workflow"
- Test the template update by following the instructions outlined here: Create wiki page to document test procedure for issues that modify issue templates #4786 (comment) (Be sure to include your URL from testing in your PR).
Resources/Instructions
- GitHub's template documentation- General information about templates; note we use .md files for our templates.
- Context for how H4LA uses issue templates: https://github.com/hackforla/website/wiki/How-to-create-issues#step-2-choose-the-right-template
- IM Populate github-handle Template file
- Populate github-handle Template file
Metadata
Metadata
Assignees
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueP-Feature: Projects pagehttps://www.hackforla.org/projects/https://www.hackforla.org/projects/role: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hours
Type
Projects
- StatusShow more project fieldsPrioritized backlog
Activity