hackforla / hackforla/website

ER: Issue templates are missing prerequisite text

Open Beginner friendly
#8,777 2 comments 0 reactions 0 assignees View on GitHub
Complexity: See issue making label ER Feature: Infrastructure Issue Making: Level 2 non-PR contribution ready for merge team role: back end/devOps role: front end size: 0.25pt
Dominant language
JavaScript
Stars
363
Forks
872
Avg merge
2d 21h
Merged PRs (30d)
18

Description

### Emergent Requirement - Problem
The Blank Issue Template and Emergent Request template do not have the Prerequisite section at the top of the template body

### Issue you discovered this emergent requirement in
- N/A

### Date discovered
9/7/2026

### Did you have to do something temporarily
- [ ] YES
- [x] NO

### Who was involved
@daras-cu

### What happens if this is not addressed
Individuals who have not completed onboarding may attempt to assign themselves to issues. This will prevent issues from being available to members as they will have to be cleaned up and re-prioritized by merge team/dev leads.

### Resources
- [Example of template with prerequisite section](https://github.com/hackforla/website/issues/new?template=add-github-handle.md)-Compare to the below templates missing this section
- [Blank Issue Template](https://github.com/hackforla/website/issues/new?template=blank-issue-template.md)
- [Emergent Request](https://github.com/hackforla/website/issues/new?template=emergent-request.md)-Missing prerequisite section at top
- [GitHub's template documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)-General information about templates; note we use .md files for our templates

### Recommended Action Items
- [ ] Make a new issue
- [ ] Discuss with team
- [ ] Let a Team Lead know

### Potential solutions [draft]
- [ ] Create a small issue for each of the Blank Issue and Emergent Request templates to add the following text to the top of the template body:
```
### Prerequisite
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).
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).
```
- [ ] Include an action item with these [instructions for template update PRs](https://github.com/hackforla/website/issues/4786#issuecomment-1670584024)

Contributor guide

Open the contributing guide

Research direction

Start by opening the existing add-github-handle.md template linked in the issue, then compare it with blank-issue-template.md and emergent-request.md. Add the specified Prerequisite section at the top of both missing templates and verify that each GitHub issue form displays the onboarding links and instructions correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, markdown
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.