Repository navigation
📖 docs: add CONTRIBUTING.md and link the community meeting from the issue chooser - #384
Conversation
…ue chooser GitHub showed the org-wide guide, whose v4/v5 branch rules are hive's. The repo guide names main, the local checks, starter issues and where to ask; contributing.test.mjs and issue-forms.test.mjs keep the links. Closes #383 Signed-off-by: outreach <280983584+hivecommons-hive[bot]@users.noreply.github.com> Co-authored-by: clubanderson <407614+clubanderson@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 the diff against a fresh checkout of main. Looks correct to me.
What I verified:
- Every path
CONTRIBUTING.mdpoints at exists:scripts/check-links.test.sh,scripts/check-redirects.test.sh,scripts/check-redirects.sh,scripts/update-csp-hashes.mjs,make-redirects.sh(with/discordand/meetin itsMAP, lines 14/24),.github/pull_request_template.md,sitemap.xml,llms.txt. - The README anchor
#local-preview-and-running-the-checksmatches the heading atREADME.md:433. scripts/contributing.test.mjsis picked up by the existingnode --test scripts/*.test.mjsstep in.github/workflows/links.yml:86, so the new gate runs in CI without wiring changes; README## Checksdocuments it asci-wiring.test.mjsrequires.issue-forms.test.mjsfails on the pre-changeconfig.yml(no meetings URL), so the new assertion is exercised.
Docs-only, no runtime surface. Nothing further from me.
— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88
|
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor. Reviewed by Reviewer notesRead against the tree at Verified:
CI is green on |
Why
This repo had no
CONTRIBUTING.md, so GitHub's new-issue and new-PR pages linked the org-wide guide. That guide tells contributors "v4 is the default branch", which is true ofhivecommons/hiveand wrong here. It also says nothing about this repo's real rules: generated redirects, CSP hashes,llms.txtparity and thenode --testgates. A newcomer to the site that fronts every Hive Commons project got no pointer to starter issues and no route to the community meeting. Every other managed repo's issue chooser already links that meeting.The new guide is short on purpose. It points at the README checks and the PR template checklist rather than restating them, and it defers to the org guide for review, governance and the AI-agent policy. That matches homebrew-hive#297 and docs#702.
The tests fail without the change:
contributing.test.mjsfails with noCONTRIBUTING.md, andissue-forms.test.mjsfails on the oldconfig.yml. The new gate is described in README## Checks, asci-wiring.test.mjsrequires.Closes #383
Claim evidence
main, the default branch:git ls-remote/ repo default branch ismain;.github/workflows/links.ymlruns on PRs and pushes tomain(README "Checks").v4/v5text:hivecommons/.githubCONTRIBUTING.md§ "Branches and Targets"..github/pull_request_template.md"Checks run locally".llms.txtrules:.github/pull_request_template.md"Checklist"./discordand/meetare entries in themake-redirects.shMAP.good first issueandhelp wantedlabels exist:gh label list --repo hivecommons/hivecommons.github.io..github/ISSUE_TEMPLATE/site_problem.yml.hivecommons/hotshot.github/ISSUE_TEMPLATE/config.yml. The page returns HTTP 200, and the homepage lists the meeting (index.html: "Biweekly meeting, Thursdays 10:00 AM ET").Checks run locally
node --test scripts/*.test.mjs: 922 pass, 0 failscripts/check-links.sh: 0 internal errors. The 2 external failures (linuxfoundation.org/trademark-usage404) were already there and CI treats them as warnings via--external-warnscripts/check-links.test.shscripts/check-redirects.shFiled by outreach agent (ACMM L6 — full mode)
— hive: agent=outreach backend=copilot model=claude-opus-5.5 copilot=1.0.88