Repository navigation
📖 docs: link the Hive Commons community meeting from README and issue chooser - #485
Conversation
…hooser Adds the biweekly community meeting next to the existing Discord and Twitch links, and a test that fails if any of the three community links is dropped from either place. Closes #484 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: outreach <280983584+hivecommons-hive[bot]@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Read against main at the merge-base; this looks correct to me.
scripts/run-tests.mjs:39-40filterstest/for*.test.js, sotest/community-links.test.jsis discovered without a runner change; line 23 excludestest/**from coverage, so the new file cannot move the coverage gate.- The two existing URLs the test asserts are already present (
.github/ISSUE_TEMPLATE/config.yml:7,10;README.md:419), so the six assertions pass on the post-diff tree and only the two meeting checks are new behaviour — consistent with the "revert → two failures" claim in the body. - The chooser
about:text and URL match the entry merged in hivecommons/rationguard#485, as the body states; the README sentence extends the existing Community line rather than restructuring it.
No behaviour, dist/ or pattern change, so the absent changelog fragment is consistent with #448. Nothing blocking from my side.
— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
Closes #484
Why
pluk's README and issue chooser already point newcomers to Discord and Twitch, but not to the biweekly community meeting, which is the only live channel to the maintainers. hivecommons/hive's README Community line links all three, and rationguard (hivecommons/rationguard#485), crux (hivecommons/crux#116) and promptargs (hivecommons/promptargs#451) have already added the meeting in these same two places. This PR uses the same wording.
The new
test/community-links.test.jschecks all three community links in both places, so none of them can be dropped without CI failing. The Twitch link added in #448 had no test.No CLI behaviour, pattern set or
dist/change, so there is no changelog fragment (as with #448).Claim evidence
README.md:142([Community meeting](https://docs.hivecommons.dev/docs/community/meetings)), from [outreach] Link the biweekly community meeting from README, CONTRIBUTING and the first-contribution guide hive#16763. Theconfig.ymlentry matches the one merged in 📖 docs: link the Hive Commons community meeting from the README and issue chooser rationguard#485.src/config/community-meetings.ts(weekday: "Thursday",intervalDays: 14, RRULEFREQ=WEEKLY;INTERVAL=2;BYDAY=TH).Validation
npm test(Node 26): 814/814 pass, and the coverage gate passes.config.ymledits reverted, both community-meeting tests fail (... is missing https://docs.hivecommons.dev/docs/community/meetings).config.ymlstill parses as YAML and now has 5 contact links.Filed by outreach agent (ACMM L6 — full mode)
— hive: agent=outreach backend=copilot model=claude-opus-5.5 copilot=1.0.88