Open Archmonger opened 3 weeks ago
I tried to reproduce this in a GitHub Action via UmbrellaDocs/action-linkspector.
The directory traversal works on my side:
--- .linkspector.yml
+++ .linkspector.yml
@@ -1,3 +1,3 @@
- dirs: [ . ]
+ dirs: [ ./extensions ]
ignorePatterns:
- pattern: '^http:\/\/localhost:'
--- a/extensions/enterprise-search/README.md
+++ b/extensions/enterprise-search/README.md
@@ -139,6 +139,6 @@ Docker container: [Running Enterprise Search Using Docker][enterprisesearch-dock
[enterprisesearch-docs]: https://www.elastic.co/guide/en/enterprise-search/current/index.html
[enterprisesearch-kb]: https://www.elastic.co/guide/en/kibana/current/enterprise-search-settings-kb.html
-[es-security]: https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settings.html#api-key-service-settings
+[es-security]: https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settingx.html#api-key-service-settings
[config-es]: ../../elasticsearch/config/elasticsearch.yml
[config-kbn]: ../../kibana/config/kibana.yml
Workflow summary:
Annotations
2 errors
❌ [linkspector] extensions/enterprise-search/README.md#L142: extensions/enterprise-search/README.md#L142
Cannot reach https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settingx.html#api-key-service-settings. Status: 404
❌ Check Markdown
Process completed with exit code 1.
Describe the bug It appears that the
linkspector
github action does not even attempt to scan any files withindirs
, which I've managed to replicate on my local Windows machine as well.However, anything listed within
files
does appear to be working at the moment.To Reproduce Steps to reproduce the behavior:
linkspector
can run (either a github action or local environment).linkspector.yml
and specify anything within thedirs
setting, for example...linkspector check
and watch it not scan any files.Expected behavior Have
linkspector check
recursively scan dirs and return errors for failed links.Screenshots N/A
Additional context I am assuming it is related to the unsupported engine errors I've seen during install time on both the GH workflow and on my local machine.