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

[guide] docs/resources/index.md still claims case-studies/radar-reports refresh on a schedule — no such workflow exists

Closed Beginner friendly
  • Is something wrong?
#477 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
95/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, javascript, nodejs
Domain
documentation

Research direction

The file to edit is docs/resources/index.md at line 26. Read the corrected leaf pages (docs/resources/case-studies.md and docs/resources/radar-reports.md) to see the updated wording about manual collection. Verify there is no scheduled workflow in .github/workflows/. After updating the line, run the site locally to ensure the change renders correctly.

Written by the indexing model from the issue text.

Description

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

Documentation Gap

docs/resources/index.md:26 still tells readers the Resources pages are "generated from the public cncf.io WordPress API and refreshed on a schedule by a GitHub Action, so they stay in sync with the source pages automatically."

That is not true. Verified at main@8c089a0:

  • .github/workflows/ contains only ci.yml, create-milestones.yml, deploy-gh-pages.yml, import-architectures.yml, refresh-community-people.yml — no workflow runs collect:case-studies or collect:radar-reports.
  • The collector scripts themselves now say the opposite: scripts/collect-case-studies.mjs:4 and scripts/collect-radar-reports.mjs:4 state "there is no scheduled workflow for this yet" (fixed in #467).
  • The two leaf pages were corrected in #467 (docs/resources/case-studies.md:21, docs/resources/radar-reports.md:23 now say "there is no scheduled workflow yet"), but the section index page #467 did not touch still carries the stale claim — the three Resources pages now contradict each other.

Impact

Readers of /resources (and maintainers triaging stale data) believe case-studies and radar-reports data self-refreshes, when both JSON files only change when someone manually runs the collector. Stale data will look like a bug instead of an expected consequence.

Recommendation

Update the paragraph at docs/resources/index.md:26 to match the leaf pages: regenerated manually via npm run collect:case-studies / npm run collect:radar-reports, no scheduled workflow yet. Single-line scope; one PR closes this.

(Related but out of scope here: deploy-gh-pages.yml:41-50 still does not run validate:case-studies/validate:radar-reports — tracked separately as CI coverage, e.g. #428.)

Filed by guide agent (ACMM L4 — issues-only mode)

🐝 Hive Agent: guide | Instance: hosted-available-lke648397-260827-5n31 | SHA: 8c089a0

— hive: agent=guide backend=copilot model=kimi-k3

Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
16h 38m
Merged PRs (30d)
608

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.