[repo-assist:maintenance] githubnext/gh-cao maintenance fix-broken-doc-links review
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Review the link changes in the five named files under docs/ and specs/operational-value-history.md. The issue says a link-existence script confirms the targets resolve; run npm run docs:build and confirm it passes before accepting the patch.
Written by the indexing model from the issue text.
Description
Six documentation links point to nonexistent files; the proposed patch retargets them, and a link-existence script confirms they now resolve. docs:build was not run because astro is not installed in the sandbox.
Action: A maintainer should review the bundle and apply it, accepting once npm run docs:build passes.
catalog.mdbecomesmarketplace.mdindocs/architecture-at-a-glance.md,docs/author-your-first-operation.md,docs/setup-multiple-organizations.md,docs/setup-one-organization.mdanddocs/setup-fine-grained-pat.md../activity.mdbecomes../docs/activity.mdinspecs/operational-value-history.md.
Agent prompt
In docs/architecture-at-a-glance.md, docs/author-your-first-operation.md, docs/setup-multiple-organizations.md, docs/setup-one-organization.md and docs/setup-fine-grained-pat.md, replace the link target catalog.md with marketplace.md. In specs/operational-value-history.md, replace ./activity.md with ../docs/activity.md. Run npm run docs:build.
cao: githubnext/gh-cao, correlation: 43278394727-169
Generated by 🔧 Repo Assist / Maintenance · copilot · auto (Claude Sonnet 5.5) · ~22 AIC · ⌖ ~2 AIC · ⊞ 15.5K · ◷
- expires on Nov 26, 2026, 6:28 PM UTC
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 4
- Avg merge
- 4h
- Merged PRs (30d)
- 708
Getting set up
- No Dockerfile or Docker Compose file
- No 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 githubnext/gh-cao
-
self-care self-care:agent-discoverability
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-cao#20928 ·
Maintainers usually reply within 1 day
-
dependabot
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-cao#20776 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
githubnext/gh-cao#20705 ·
Maintainers usually reply within 1 day
-
[uk-ai-advisory:operational-resilience] UK AI advisory: operational resilience for githubnext/gh-caoOpenuk-ai-advisory uk-ai-advisory:operational-resilience
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-cao#20669 ·
Maintainers usually reply within 1 day
-
self-care self-care:documentation-discoverability
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-cao#20667 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-cao
Similar issues
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dlq/synthpopcan#58 ·
Maintainers usually reply within 2 days
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fjaeckel/seriesoftubes#376 ·
Maintainers usually reply within 1 day