-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
False-positive errors: invalid URL, awesome-git-repo-age, no-defined-references, no-repeat-punctuation, invalid git repository. #191
Comments
I followed @tapyu's suggestion to run awesome-lint again within the local git directory. The invalid URL and invalid repo errors weren't thrown again. But the other errors are still there:
ErrorsRepo ageUndefined definitionGithub alerts syntax was detected as undefined definitions. > [!TIP]
> All resources in this curated list are free, unless otherwise noted. Repeated punctuationAll the ellipsises (...) are detected as repeated dots. [Everything You Want to Know about ...](https://learn.microsoft.com/en-us/powershell/scripting/learn/deep-dives/everything-about-arrays?view=powershell-7.4) |
I replaced I still got 3 kinds of errors:
Double links
If remove one of the VS Code link, one of the lists will be incomplete. |
The issue regarding repo age may be due to this reason |
@batrdn The I ever removed several commits using git commands and force push to the GitHub repository. Maybe these operations caused the |
@wongyah ahh I see, then probably has nothing to do with it. |
Error message
After running awesome-lint on my repo Awesome Technical Writing Learning, I got the following error messages:
Summary
There are five kinds of false-positive errors above:
Invalid URL
Repository URL:
https://github.com/wongyah/awesome-technical-writing-learning
.Repo age
Invalid git repository
em ...
Undefined definition
Github alerts syntax was detected as undefined definitions.
Repeated punctuation
All the ellipsises (
...
) are detected as repeated dots.The text was updated successfully, but these errors were encountered: