Add Prerequisite section to the Emergent Request template
Maintainers usually reply within 2 days
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, markdown
- Domain
- documentation
Research direction
Open .github/ISSUE_TEMPLATE/emergent-request.md and compare it with .github/ISSUE_TEMPLATE/add-githib-handle.md, then review the linked GitHub template documentation. Add the requested Prerequisite section above Overview and test the template using the instructions in issue #4786, including the resulting URL in the pull request.
Written by the indexing model from the issue text.
Description
Overview
We need to directly clarify who should be assigning themselves to issues by adding a Prerequisite section to the top of the Emergent Request template. This prevents contributors who haven't completed onboarding from self-assigning issues, which helps keep issues available to active members and reduces cleanup/re-prioritization work for the merge team and dev leads.
Action Items
- Open the
.github/ISSUE_TEMPLATE/emergent-request.mdfile. - Add a
###Prerequisitesubheading above###Overview - Add this text to that new section:
1. 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](https://www.hackforla.org/getting-started) and attend an onboarding session.
2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).
- 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
- refer to
.github/ISSUE_TEMPLATE/add-githib-handle.mdas an example of an issue template .md file with a###Prerequisitesection. Here is a link to what that looks like in Github: https://github.com/hackforla/website/issues/new?template=add-github-handle.md - 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
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 873
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 11
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: Small P-Feature: Projects page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
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 Status: Unassigned by Bot time sensitive
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hackforla/website#8806 · 1 comment ·
Maintainers usually reply within 2 days
-
Complexity: Small Feature: Infrastructure Ready for Prioritization role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
Complexity: Small Draft ER Issue Making: Level 1 P-Feature: Projects 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 · 3 comments ·
Maintainers usually reply within 2 days
-
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 2 days
All issues in hackforla/website
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
solana-foundation/solana-com#2202 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
yegor256/copyrights-action#216 ·
-
[BUG] onScroll never refreshes the window container's height after a vertical-only viewport resizeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
juliangarnier/anime#1192 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PedestrianDynamics/pyFDS-Evac#226 ·
Maintainers usually reply within 1 day