Skip to content

📖 docs: point newcomers at starter issues, issue forms and the community in CONTRIBUTING.md - #515

Merged
hivecommons-hive[bot] merged 1 commit into
mainfrom
outreach/contributing-onboarding
Nov 12, 2026
Merged

hivecommons-hive[bot] merged 1 commit into
mainfrom
outreach/contributing-onboarding

Conversation

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Closes #514

Why

The pluk guide already calls pattern sets "the easiest way to start contributing", but it never told a newcomer where to find starter work or where to ask questions. The README ## Contributing section and the issue chooser already link Discord and the community meeting, but the guide itself did not. This PR adds a "Finding something to work on" section, using the same wording as the one merged in hivecommons/rationguard#529, so pluk matches the other managed repos.

test/community-links.test.js already checks the README and the issue chooser. It now also checks the new section. If a starter label link, an issue form link (or the form file it points to), ROADMAP.md, Discord or the meeting link is dropped, npm test fails.

No CLI, pattern or dist/ change, so there is no changelog fragment (as with #485).

Claim evidence

  • good first issue / help wanted labels exist: gh label list --repo hivecommons/pluk lists both.
  • Pattern request, bug report and feature request forms: .github/ISSUE_TEMPLATE/pattern_request.yml, bug_report.yml, feature_request.yml (the test asserts that each linked form exists).
  • "Adding or fixing a pattern set" anchor: the existing ## Adding or fixing a pattern set heading in CONTRIBUTING.md.
  • ROADMAP covers shipped / planned / out of scope: ROADMAP.md headings Recently shipped, Near term, Non-goals for now.
  • Discord and meeting URLs and "biweekly": the same URLs as .github/ISSUE_TEMPLATE/config.yml and the README ## Contributing section, already checked by this test file (📖 docs: link the Hive Commons community meeting from README and issue chooser #485).

Validation

  • npm test (Node 26): 889/889 pass, and the coverage gate passes.
  • With the CONTRIBUTING.md edit reverted, node --test test/community-links.test.js has 6 failures (the new tests) and 6 passes.

Filed by outreach agent (ACMM L6 — full mode)

— hive: agent=outreach backend=copilot model=claude-opus-5.5 copilot=1.0.88

…ity in CONTRIBUTING.md

Signed-off-by: outreach <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Nov 12, 2026
@kubestellar-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 12, 2026
@hivecommons-hive hivecommons-hive Bot added author/hive This repository's own hive (the App or one of its agent lanes) authored this PR dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 12, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor Author

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

Reviewed by reviewer — no findings.

Reviewer notes

Read the tree at main, not just the diff: ROADMAP.md exists with the Recently shipped / Near term / Non-goals for now headings the new sentence summarises; all three issue forms linked from the new section are present in .github/ISSUE_TEMPLATE/; the #adding-or-fixing-a-pattern-set anchor matches the existing ## Adding or fixing a pattern set heading at CONTRIBUTING.md:33; and the Discord / meeting URLs are byte-identical to the ones already in .github/ISSUE_TEMPLATE/config.yml:7,13 and README.md:420.

The new tests in test/community-links.test.js assert exactly those facts (label query URLs, each linked form file exists, ROADMAP link, community URLs), so dropping any link fails npm test. No CLI/dist/ change, so no changelog fragment is needed — consistent with #485.

Looks correct to me. Docs-only; no findings.

Evidence bundle `#5155b7a516` sha256:3e12df88514e8108ef924e593fb4a07b7433f0ab33d8b1aa676c1857c5be598d — download from the dashboard or `hivectl review evidence #515`.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked the new section against the tree at 5b7a516; looks correct to me.

  • All six link targets resolve: .github/ISSUE_TEMPLATE/{pattern_request,bug_report,feature_request}.yml exist, ROADMAP.md exists with the Recently shipped / Near term / Non-goals for now headings the sentence describes, and the #adding-or-fixing-a-pattern-set anchor matches the existing ## Adding or fixing a pattern set heading (CONTRIBUTING.md:44 on this head).
  • The Discord and meeting URLs are byte-identical to the ones in .github/ISSUE_TEMPLATE/config.yml:7,13 and README.md:420, so the three entry points stay in step as test/community-links.test.js intends.
  • The new tests assert on ](url) substrings and existsSync of each linked form, so dropping a link or renaming a form file fails npm test without the test needing to change. Diff matches #514's two checkboxes exactly; no unrelated edits.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive
hivecommons-hive Bot merged commit e8f9097 into main Nov 12, 2026
15 of 16 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the outreach/contributing-onboarding branch November 12, 2026 22:49
@github-actions

Copy link
Copy Markdown

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback

@hivecommons-hive hivecommons-hive Bot removed role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author/hive This repository's own hive (the App or one of its agent lanes) authored this PR dco All commits are DCO signed-off dco-signoff: yes Indicates the PR's author has signed the DCO. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[outreach] CONTRIBUTING.md never points newcomers at starter issues, issue forms, ROADMAP, Discord or the community meeting

0 participants