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

Decide whether lychee should be run on the standalone workflow #52

Open
artur-rs opened this issue Oct 2, 2024 · 0 comments
Open

Decide whether lychee should be run on the standalone workflow #52

artur-rs opened this issue Oct 2, 2024 · 0 comments
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. An enhancement or improvement of existing functionality. W: todo Workflow: todo. The issue is in the initial to do state.

Comments

@artur-rs
Copy link

artur-rs commented Oct 2, 2024

The problem you're addressing (if any)

The lychee CI check is either skipped or doesn't work. It can be caused by the wrong version of the docker or a network problem. https://results.pre-commit.ci/run/github/202936662/1727443270.BVwXoc4tS5mqTu9cyQeFlQ

Describe the solution you'd like

Let's decide whether to migrate the lychee check on the new CI workflow.

Where is the value to a user, and who might that user be?

Describe alternatives you've considered

Additional context

Relevant documentation you've consulted

Dasharo/docs had the same problem, and it was moved to a different workflow:
https://github.com/Dasharo/docs/blob/master/.github/workflows/seo.yml

Related, non-duplicate issues

@artur-rs artur-rs added T: enhancement Type: enhancement. An enhancement or improvement of existing functionality. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. W: todo Workflow: todo. The issue is in the initial to do state. labels Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. An enhancement or improvement of existing functionality. W: todo Workflow: todo. The issue is in the initial to do state.
Projects
None yet
Development

No branches or pull requests

1 participant