Update Help Wanted issue search
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- documentation
Research direction
Open README.md and locate the help-wanted label hyperlink in the “Not sure where to start?” section at the bottom. Add +OR+org%3Ablowhorn-ai to its existing search URL while preserving the current organizations. Verify that the link includes open help wanted issues from blowhorn-ai.
Written by the indexing model from the issue text.
Description
Description
The Help Wanted issue search in README.md currently covers several Layer5-related GitHub organizations, but it does not yet include the newly added [blowhorn-ai](https://github.com/blowhorn-ai) organization.
The search link appears in the "Not sure where to start?" section at the bottom of the README as the help-wanted label hyperlink.
This link should be updated to include blowhorn-ai.
Proposed Change
Add the following to the existing search query:
+OR+org%3Ablowhorn-ai
This will include open help wanted issues from the new organization while keeping all existing organizations in the search.
Acceptance Criteria
- Update the help-wanted label hyperlink at the bottom of the README.
- Add
+OR+org%3Ablowhorn-aito the existing search URL. - Verify that the updated link includes
help wantedissues fromblowhorn-ai. - Preserve all existing organizations in the search.
- Dominant language
- Go
- Stars
- 162
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 layer5io/getnighthawk
-
Add pruning for PR preview deploymentsPossibly taken @Yashisinghal285 claimed this 136 days ago. Openkind/enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
layer5io/getnighthawk#377 · 2 comments ·
-
Poor styling in Home page and other page leading in misallignment of containers and elementPossibly taken @iamundefinedguy claimed this 829 days ago. Openkind/bug
layer5io/getnighthawk#359 · 4 comments · 1 assignee ·
-
[CI] Add Label CommenterMay be free again @sandramsc claimed this 1057 days ago, and no pull request is open. Openkind/enhancement
layer5io/getnighthawk#354 · 1 assignee ·
-
[Bug] small issue in the vertical navbar link cssPossibly taken @omesh-omg claimed this 1074 days ago. Openkind/bug
layer5io/getnighthawk#350 · 7 comments · 1 assignee ·
-
[Documentation] update the CONTRIBUTING.md with Issues & Pull Requests sectionsMay be free again @sandramsc claimed this 1136 days ago, and no pull request is open. Openarea/docs
layer5io/getnighthawk#338 · 2 comments · 1 assignee ·
All issues in layer5io/getnighthawk
Similar issues
-
bug from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#14868 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
project-zot/zot#4636 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
keyxmakerx/Chronicle#1911 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
eugenioenko/ttt#1293 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
needs/area needs/kind needs/priority
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day