[guide] CONTRIBUTING says data/projects-born.json has no validation script — validate:projects-born now exists and gates CI
Maintainers usually reply within 1 day
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
- javascript
- Domain
- documentation
Research direction
Start in CONTRIBUTING.md at the ProjectsBorn table row around line 68 and the rules list around line 102. Check scripts/validate-projects-born.mjs, package.json, and .github/workflows/ci.yml to confirm the command and CI usage. Done means both stale statements mention npm run validate:projects-born and the documentation matches the repository’s current validation behavior.
Written by the indexing model from the issue text.
Description
Documentation Gap
CONTRIBUTING.md's data contribution model is stale after PR #753 (merged in 10e70b5). It states twice that data/projects-born.json has no validation:
- The table row (line 68):
ProjectsBorn (/practitioners) | data/projects-born.json | manual edit, no validation script - The rules list (line 102):
data/projects-born.json has no generator; edit it directly
But PR #753 added scripts/validate-projects-born.mjs (105 lines), the npm run validate:projects-born script, and a CI step in .github/workflows/ci.yml (line 61) that runs it on every PR. grep -r "validate:projects-born" --include="*.md" returns zero hits — no doc anywhere in the repo mentions the validator.
Impact
A contributor editing data/projects-born.json follows CONTRIBUTING, makes a manual edit with no local validation, and only learns the file has a strict machine-checked contract (URL allowlists, schema checks added by the security hardening in #753) when the "Validate repository" CI check fails on their PR. Every other data file in the same table documents its validator; this one now misleads.
Recommendation
- Table row: change the Validation column for ProjectsBorn to
npm run validate:projects-born - Rules bullet: keep "no generator; edit it directly" but append that the edit must pass
npm run validate:projects-born(which CI enforces), matching the pattern used for the other curated files
Single small CONTRIBUTING.md edit; one PR closes this.
Filed by guide agent (ACMM L4 — issues-only mode)
🐝 Hive Agent: guide | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown
— hive: agent=guide backend=copilot model=kimi-k3 copilot=1.0.88
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 293
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- 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 cncf/endusers
-
[quality] refresh-radar-reports.yml runs on ubuntu-latest while every other job pins ubuntu-24.04Openagent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
opensearch-project/security-dashboards-plugin#2543 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
godotengine/godot-website#1432 ·
-
Add: Mooz RetroOpenchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4007 ·
Maintainers usually reply within 1 day