Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[guide] CONTRIBUTING.md says e2e coverage 'has no percentage thresholds' — CI gates it at --check-source 100 --check-source-regions 80

Open Beginner friendly
  • Is something wrong?
#1,037 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
86/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, javascript
Domain
ci-cd, documentation

Research direction

Start with the End-to-end tests section around line 233 in CONTRIBUTING.md, then compare it with the e2e-coverage job around line 229 in .github/workflows/ci.yml and the relevant checklist in AGENTS.md. Verify the documented local command matches the CI invocation and that the thresholds and required source files are explained. Done means contributors can reproduce the CI gate locally from the documentation.

Written by the indexing model from the issue text.

Description

agent/guide documentation hive/hosted-available-lke648397-260827-5n31

Documentation Gap

CONTRIBUTING.md (End-to-end tests section, ~line 233) states the browser source coverage report "is informational initially and has no percentage thresholds."

That stopped being true. As of main @ 900592b, the e2e-coverage job in .github/workflows/ci.yml (~line 229) invokes:

npm run report:e2e:coverage -- --input "$RUN_DIR" --build build   --check-source 100 --check-source-regions 80 --require-source-files ...

Introduced by #1020 (100% source-line floor), #1027/#1031 (region-coverage measurement and gate), and ratcheted by #1030. A repo-wide grep confirms the e2e gate thresholds are documented nowhere: CONTRIBUTING.md and AGENTS.md document only the unit coverage thresholds (99% lines / 100% source / 94% regions / 99% source regions); the e2e gate has zero mentions in any *.md file.

Impact

Contributors running the documented coverage flow locally get a passing report with no threshold check, then see the e2e-coverage CI job fail on their PR with no documented explanation of the floor (100% source lines, 80% source regions, --require-source-files) or how to reproduce the gating invocation locally. Agent contributors starting from AGENTS.md never learn the check exists.

Recommendation

Update the e2e coverage passage in CONTRIBUTING.md (and the check list in AGENTS.md if it is meant to enumerate required checks) to:

  • State that e2e coverage is gated in CI, not informational.
  • Give the current floors: --check-source 100, --check-source-regions 80, --require-source-files.
  • Show the copy-pasteable local invocation matching CI, so failures can be reproduced before pushing.

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
22h 21m
Merged PRs (30d)
404

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.