When the link check job fails, it is not immediately obvious what failed.
Example: https://github.com/canonical/observability-stack/actions/runs/17603351421/job/50107180852
Lot's of "ok", and need to eyeball the failed one.
It would be great if at the end we'd get a summary of all the links that failed, or something similar to that effect.
(how-to/tiered-otelcols: line 9) ok https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/batchprocessor/README.md
(how-to/selectively-drop-telemetry: line 91) redirect https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl/README.md - permanently to https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/README.md
(reference/charms: line 13) ok https://github.com/canonical/s3-integrator/issues
(reference/charms: line 14) ok https://github.com/canonical/self-signed-certificates-operator/issues
(reference/charms: line 45) ok https://github.com/canonical/snmp-exporter-operator/issues
(how-to/tiered-otelcols: line 47) ok https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/attributesprocessor/README.md
(how-to/troubleshooting/troubleshoot-integrations: line 83) ok https://github.com/canonical/zookeeper-operator/blob/main/metadata.yaml#L31
(reference/rock-oci-images: line 21) ok https://github.com/canonical/xk6-rock/issues
(reference/charms: line 43) redirect https://github.com/canonical/prometheus-scrape-target-operator/issues - permanently to https://github.com/canonical/prometheus-scrape-target-k8s-operator/issues
(how-to/selectively-drop-telemetry: line 58) ok https://github.com/open-telemetry/opentelemetry-proto/blob/main/examples/README.md
-rate limited- https://github.com/canonical/postgresql-k8s-operator/blob/978080424255e109c7a7c4f4d23a5b3d5aba12a6/src/charm.py#L188 | sleeping...
(reference/rock-oci-images: line 18) ok https://github.com/canonical/prometheus-pushgateway-rock/issues
(explanation/logging-architecture: line 52) ok https://github.com/canonical/postgresql-k8s-operator/blob/978080424255e109c7a7c4f4d23a5b3d5aba12a6/src/constants.py#L23
(explanation/logging-architecture: line 52) ok https://github.com/canonical/postgresql-k8s-operator/blob/978080424255e109c7a7c4f4d23a5b3d5aba12a6/src/charm.py#L188
sphinx-sitemap: No pages generated for sitemap.xml
build finished with problems.
make: *** [Makefile:123: linkcheck] Error 1
Command 'make -f Makefile linkcheck' returned non-zero exit status 2.
Error: Process completed with exit code 1.
When the link check job fails, it is not immediately obvious what failed.
Example: https://github.com/canonical/observability-stack/actions/runs/17603351421/job/50107180852
Lot's of "ok", and need to eyeball the failed one.
It would be great if at the end we'd get a summary of all the links that failed, or something similar to that effect.