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

Detect errors before reporting files that are no longer referenced #376

Open
tidoust opened this issue Sep 29, 2021 · 0 comments
Open

Detect errors before reporting files that are no longer referenced #376

tidoust opened this issue Sep 29, 2021 · 0 comments

Comments

@tidoust
Copy link
Member

tidoust commented Sep 29, 2021

The action that runs to report files that are no longer referenced raises false positives when crawling errors occurred. Sometimes, these errors are not really detected as errors and there is not much we can do about that apart from manually checking the result. However, in some cases, the errors are actually detected and reported in the index.json file. The action should check these and either not run when errors were detected or skip over files that seem linked to the specs that errored.

(Inspired by #375 (review))

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

No branches or pull requests

1 participant