The Awesome Bot workflow is failing on current master, including the run for commit 5c7ecb4da445aeb5b48a6114e846ee100e05fe08 (run 35468634528). The run exits 1 after checking README.md; the same failure pattern is present on recent pushes for PRs #167, #168, and #169.
The report includes deterministic 404s (for example the Infognition Bitbucket workspace, Abscissa Goldie wiki, bmchtech/rengfx, and xomboverlord/xomb/tree/unborn), as well as redirects and access-limited responses such as 403 and 522. These should be triaged separately rather than treated as equivalent broken links.
Expected: the workflow should either pass on supported links or apply an explicit policy for redirects and access-limited URLs, while stale entries are updated or removed. This keeps the default branch signal actionable.
Existing issue #141 was a general link-cleanup discussion and is closed; this report records the current recurring CI evidence and the concrete URLs reported by the latest run.
The Awesome Bot workflow is failing on current
master, including the run for commit5c7ecb4da445aeb5b48a6114e846ee100e05fe08(run 35468634528). The run exits 1 after checkingREADME.md; the same failure pattern is present on recent pushes for PRs #167, #168, and #169.The report includes deterministic 404s (for example the Infognition Bitbucket workspace, Abscissa Goldie wiki,
bmchtech/rengfx, andxomboverlord/xomb/tree/unborn), as well as redirects and access-limited responses such as 403 and 522. These should be triaged separately rather than treated as equivalent broken links.Expected: the workflow should either pass on supported links or apply an explicit policy for redirects and access-limited URLs, while stale entries are updated or removed. This keeps the default branch signal actionable.
Existing issue #141 was a general link-cleanup discussion and is closed; this report records the current recurring CI evidence and the concrete URLs reported by the latest run.