Context
The standing report PRs from the link-health scanner and the automation
health dashboard write their generated markdown into docs/ in the org
main repo (rossoctl/rossoctl). That docs/ folder is now the source for
the documentation site (rossoctl.dev), so the site build overwrites/excludes
the machine-generated report files (see rossoctl/rossoctl#2315).
Temporary change
As a stop-gap, both report PRs are being redirected to write under
docs/reports/ in the automation repo instead of the main repo's
docs/. This keeps the reports out of the docs-site source path while a
permanent home is decided.
Decision needed (permanent placement)
- Should the generated reports live in
automation (e.g. docs/reports/),
or somewhere on the docs site now that automation and agent-skills
are core repos?
- Whatever the destination, the docs-site build must ignore machine-written
report subfolders (or the reports must live outside any build-sourced path).
Once decided, replace the temporary redirect with the permanent target.
Context
The standing report PRs from the link-health scanner and the automation
health dashboard write their generated markdown into
docs/in the orgmain repo (
rossoctl/rossoctl). Thatdocs/folder is now the source forthe documentation site (rossoctl.dev), so the site build overwrites/excludes
the machine-generated report files (see rossoctl/rossoctl#2315).
Temporary change
As a stop-gap, both report PRs are being redirected to write under
docs/reports/in theautomationrepo instead of the main repo'sdocs/. This keeps the reports out of the docs-site source path while apermanent home is decided.
Decision needed (permanent placement)
automation(e.g.docs/reports/),or somewhere on the docs site now that
automationandagent-skillsare core repos?
report subfolders (or the reports must live outside any build-sourced path).
Once decided, replace the temporary redirect with the permanent target.