Move workflow status documentation page to top level #2113
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moves the "Workflow Status" documentation page from the reference subdirectory to the top level of the documentation structure, positioning it at the bottom of the table of contents.
Changes
docs/src/content/docs/reference/status.mdtodocs/src/content/docs/status.mdscripts/generate-status-badges.jsto output to the new location999to1000to ensure the page appears at the bottom of the TOCImplementation
The status page is automatically generated by the
generate-status-badges.jsscript, which runs as a prebuild step (npm run prebuild) before the documentation build. The script:.lock.ymlworkflow files in.github/workflows/docs/src/content/docs/status.mdWith this change, the "Workflow Status" page now appears as a top-level item in the documentation navigation, separate from the "Workflows" reference section, making it easier to access the status of all agentic workflows in the repository.
Verification
/status/index.htmlwith correct sidebar positioningWarning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
telemetry.astro.buildnode /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.