Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make link checker less verbose #262

Closed
sverhoeven opened this issue Apr 30, 2021 · 0 comments · Fixed by #385
Closed

Make link checker less verbose #262

sverhoeven opened this issue Apr 30, 2021 · 0 comments · Fixed by #385

Comments

@sverhoeven
Copy link
Member

The link checker GHA workflows output is very verbose making it hard to see which links are actually broken. Can the verboseness be reduced with use-quiet-mode: 'yes' in workflow step.

Adding this flag gives

act -W .github/workflows/markdown-link-check.yml push
...
| FILE: ./{{cookiecutter.project_name}}/.github/next_steps/05_linting.md
| 
| 0 links checked.
| 
| FILE: ./{{cookiecutter.project_name}}/.github/next_steps/04_citation.md
| [✖] https://yamllint.com
| 
| 6 links checked.
| 
| ERROR: 1 dead links found!
| [✖] https://yamllint.com → Status: 0
| 
| FILE: ./{{cookiecutter.project_name}}/.github/next_steps/02_zenodo_integration.md
| 
| 0 links checked.
| 
...

Which I think is much easier to find dead links then with

| FILE: ./{{cookiecutter.project_name}}/.github/next_steps/05_linting.md
| No hyperlinks found!
| 
| 0 links checked.
| 
| FILE: ./{{cookiecutter.project_name}}/.github/next_steps/04_citation.md
| [/] {{cookiecutter.repository}}/actions/workflows/cffconvert.yml
| [✓] https://github.com/citation-file-format/citation-file-format
| [✓] https://orcid.org/
| [✓] https://help.zenodo.org/
| [✖] https://yamllint.com
| [✓] https://jsonlint.com/
| 
| 6 links checked.
| 
| ERROR: 1 dead links found!
| [✖] https://yamllint.com → Status: 0
| 
| FILE: ./{{cookiecutter.project_name}}/.github/next_steps/02_zenodo_integration.md
| No hyperlinks found!
| 
| 0 links checked.

I don't care if links are working, so I would rather not see them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant