Wrong filename output

[koppor]

Output:

=========================> MARKDOWN LINK CHECK <=========================


FILE: docs/jpackage.md
[✖] https://github.com/YOUR_USERNAME/jabref → Status: 404


FILE: docs/adr/0004-use-mariadb-connector.md
[✖] https://github.com/JabRef/jabref/wiki/Translating-JabRef-Help → Status: 429
[✖] https://github.com/JabRef/jabref/blob/master/src/main/java/org/jabref/logic/formatter/bibtexfields/NormalizePagesFormatter.java → Status: 429

(Source: https://github.com/JabRef/jabref/pull/6524/checks?check_run_id=714600307)

The link with YOUR_USERNAME appears in a different file:

Same for the other block:

Is it possible to output the correct file name?

My config:

      - name: Run markdown-link-check
        uses: gaurav-nelson/github-action-markdown-link-check@v1
        with:
          use-quiet-mode: 'yes'
          use-verbose-mode: 'yes'
          config-file: 'mlc_config.json'
          folder-path: 'docs/'

[gaurav-nelson]

Thanks @koppor for reporting this.

Can you please turn off the quiet mode and check the full log once?

- name: Run markdown-link-check
        uses: gaurav-nelson/github-action-markdown-link-check@v1
        with:
          use-verbose-mode: 'yes'
          config-file: 'mlc_config.json'
          folder-path: 'docs/'

For verbose mode, the script parses the whole output and lists errors, it might have some logic issue. The full log will help me debug the issue.

[koppor]

It's not as easy as I thought:

Did I configure something wrong?

      - name: Run markdown-link-check
        uses: gaurav-nelson/github-action-markdown-link-check@v1
        with:
          use-quiet-mode: 'no'
          use-verbose-mode: 'yes'
          config-file: 'mlc_config.json'
          folder-path: '/docs'

[JoshOrndorff]

I also encountered this here https://github.com/substrate-developer-hub/recipes/runs/743069911

The issue happens in quiet mode but goes away when I disable quiet mode.

[gaurav-nelson]

Thanks @koppor @JoshOrndorff

I've released version 1.0.3 to fix this. Also, updated the v1 tag to point to this release.

[JoshOrndorff]

Confirmed this is working for me. Thank you.