[shatrughantwt]

Description

Updated the help-wanted issue search link in README.md to include the blowhorn-ai organization.

Changes

• Added blowhorn-ai to the existing GitHub issue search query.
• Preserved all existing organizations and filters.

Notes for Reviewers

This PR fixes #1889

Signed commits

• Yes, I signed my commits.

Summary by CodeRabbit

• New Features
  • The community “help wanted” link now includes issues from the meshery-extensions and blowhorn-ai organizations in its search results, making more help-wanted opportunities available from one place. This expands the organizations represented in the link’s results while keeping the existing community link and search experience unchanged.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The README help-wanted issue search URL now includes issues from the blowhorn-ai organization.

Changes: Help-wanted search

Layer / File(s)	Summary
Update help-wanted search URL README.md	The search URL adds blowhorn-ai to its organization filters.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · up to 26f6e

The help-wanted link includes blowhorn-ai without changing the existing search scope or filters. The change is ready to merge.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly summarizes the README change by identifying the addition of blowhorn-ai to the help-wanted search.
Linked Issues check		[#1889] Requirement: add +OR+org%3Ablowhorn-ai to the help-wanted search link in the "Not sure where to start?" section, and keep all existing organizations. The whole-PR diff from merge base fcaa15…
Out of Scope Changes check		The whole-PR diff from merge base fcaa158 to head 26f6e40 contains one hunk in README.md. The hunk changes only the help-wanted search link named in #1889. It adds the blowhorn-ai organization term …
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…

Full details: Linked Issues check

Explanation

[#1889] Requirement: add +OR+org%3Ablowhorn-ai to the help-wanted search link in the "Not sure where to start?" section, and keep all existing organizations. The whole-PR diff from merge base fcaa158 to head 26f6e40 changes one README.md line. The base link query is (org%3Alayer5io OR org%3Ameshery OR org%3Alayer5labs OR org%3Aservice-mesh-performance OR org%3Aservice-mesh-patterns OR org%3Ameshery-extensions). The head link query is the same, with +OR+org%3Ablowhorn-ai added before the closing parenthesis. The filters is%3Aopen+is%3Aissue+archived%3Afalse and label%3A%22help+wanted%22 are unchanged. This meets each acceptance criterion: the help-wanted hyperlink is updated, the term is added, existing organizations are preserved, and the query includes open help wanted issues from blowhorn-ai. The meshery-extensions term was already present at the base, so the AI summary that lists it as added is inaccurate. The change since the previous review (d3b5e28 to 26f6e40) does not alter this README line in the whole-PR diff. The live GitHub search result was not run. The verdict rests on query logic, which is the change the issue requests. No coding tests apply to this README-only change.

Full details: Out of Scope Changes check

Explanation

The whole-PR diff from merge base fcaa158 to head 26f6e40 contains one hunk in README.md. The hunk changes only the help-wanted search link named in #1889. It adds the blowhorn-ai organization term and changes no other text, link, code, or configuration. The raw summary reports +1/-1 lines, which matches this single-line change. No out-of-scope change is present.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 92cae016-0df4-48ab-b100-690c5f5c1fa9

Commits

Reviewing files that changed from the base of the PR and between d3b5e28 and 26f6e40.

Files selected for processing: 1

• README.md

Files skipped from review as they are similar to previous changes: 1

• README.md

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.

[miacycle]

Nice catch, and a clean one line change. Adding blowhorn-ai to the help-wanted search keeps the README newcomer pointer in step with the orgs where help-wanted issues now live, so new contributors do not miss Blowhorn work.

I checked the updated query string against the existing pattern for the other orgs, and only the new OR clause was added, so the search syntax stays consistent.

One small check before merge: does the linked search return Blowhorn help-wanted issues as expected when signed out? If so, this looks good to go from my side.

[shatrughantwt]

Nice catch, and a clean one line change. Adding blowhorn-ai to the help-wanted search keeps the README newcomer pointer in step with the orgs where help-wanted issues now live, so new contributors do not miss Blowhorn work.

I checked the updated query string against the existing pattern for the other orgs, and only the new OR clause was added, so the search syntax stays consistent.

One small check before merge: does the linked search return Blowhorn help-wanted issues as expected when signed out? If so, this looks good to go from my side.

I tested both links. both the original and updated search URLs return 404 when signed out,They work when signed in, Looks like a GitHub search limitation, not an issue with the new query. Blowhorn issues show up correctly when signed in.