Include a fail_level in the check links ci files

[Adrian D'Alessandro (AdrianDAlessandro)]

Description

It appears that the Linkspector action will not fail on bad links unless a fail_level is set as a parameter (see this PR in DIRECT web app). This PR adds it to both workflows in this repo.

Type of change

• Documentation (non-breaking change that adds or improves the documentation)
• New feature (non-breaking change which adds functionality)
• Optimization (non-breaking, back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (whatever its nature)

Key checklist

• All tests pass (eg. python -m pytest)
• Pre-commit hooks run successfully (eg. pre-commit run --all-files)

Further checks

• Code is commented, particularly in hard-to-understand areas
• Tests added or an issue has been opened to tackle that in the future.
  (Indicate issue here: # (issue))

[Copilot]

Pull request overview

This PR updates the Linkspector GitHub Actions workflows to ensure link checking fails the CI job when broken links are detected by setting the fail_level input.

Changes:

• Add fail_level: any to Linkspector steps in the repository workflow.
• Add fail_level: any to Linkspector steps in the cookiecutter template workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/check-links.yml	Adds fail_level to Linkspector action configuration so broken links fail CI.
{{ cookiecutter.project_slug }}/.github/workflows/check-links.yml	Mirrors the same fail_level behaviour in the generated project template workflow.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Diego Alonso Álvarez (dalonsoa)]

OK. Weird that the default behaviour of a tool that check links is not failing when it finds links that are not working.