Doubt about awesome-lint double-link error

[niedev]

If the double links are in the description of two different elements (because they both are a fork of the linked repository) is this still considered an error? as if I didn't respect the guidelines?

[sindresorhus]

I think we should only lint the list items for double links. Not their description, and not any other text.

// @Scrum

[Scrum]

If the double links are in the description of two different elements (because they both are a fork of the linked repository) is this still considered an error? as if I didn't respect the guidelines?

Only links are checked, describe your problem in more detail

[niedev]

For example, if I have these two elements in the readme:

• Lawnchair 2 - Continuation of Lawnchair 1; Pixel features; fork of Launcher3.
• Librechair - Degoogled; fork of Lawnchair V2 & Launcher3.

Awesome-lint will notify double-link error for the Launcher3 links in the descriptions.

[Scrum]

I still can't figure out why we shouldn't check the links in the paragraph and the link description?

I believe that if there are more than one links, then it already looks like a repository pair. The link or paragraph should contain a general description that characterizes the package.

[morinted]

My false positive for this rule came from my preamble, where I linked to the project by its [name](github.com/project/name) and in the link given on the logo, which was recommended in the awesome-list guidelines.

[wongyah]

I got the same error (double links) because of the links in item descriptions and connecting paragraphs.

I deleted all these kinds of links now to compliant with the awesome-lint rules, but I think I paid the price of readability. I will add these links back when the bug is fixed.