Update Template: 'Issue Making Populate github-handle'
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- documentation
Research direction
Open .github/ISSUE_TEMPLATE/issue-making-populate-github-handle-for-project.md and compare its Action Items with the requested wording. Read the testing steps in issue #4786, then follow them to verify the updated template and include the resulting URL in the PR. Done means the instruction accurately explains replacing the placeholder with the member's GitHub username.
Written by the indexing model from the issue text.
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.
- 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`
- Test the template update by following the instructions outlined here: https://github.com/hackforla/website/issues/4786#issuecomment-1670584024 (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
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 873
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 8
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: See issue making label epic good first issue Issue Making: Level 1 non-PR contribution P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Complexity: Small Feature: Board/GitHub Maintenance ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Complexity: Small Feature: Board/GitHub Maintenance ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Complexity: Small ER Issue Making: Level 2 P-Feature: Home page ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hackforla/website#8803 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue new-win-submission P-Feature: Wins Page role: product size: missing
Difficulty 1/5 Under an hour Newbie friendliness 85/100
hackforla/website#8798 · 1 comment ·
Maintainers usually reply within 1 day
All issues in hackforla/website
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
amponce/archive-movie-browser#354 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
saayam-for-all/webapp#1870 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Imageomics/OpenCite#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
chr15m/twiiit.com#20 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
antropos17/Aegis#629 ·
Maintainers usually reply within 4 days