-
Notifications
You must be signed in to change notification settings - Fork 279
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
🚀 Feature: awesome linting workflow #324
Comments
@saintmalik very sorry for the delay in responding and thanks a lot for suggesting this feature. I would love to know if you have worked with Awesome Linting in the past and whether it allows custom formatting since we recently restructured the entire Readme? |
Yeah, i have worked with Awesome Linting in the past, i use it in one of my projects, what do you mean by custom formatting?, so after running a linting test here are the results.
Seems its the custom formatting that caused most errors right? |
@adityaoberai if you don't mind. I'd like to work on this issue and improve GitHub actions with awesome linting rules. |
At the moment, since we follow custom formatting purposefully, and we don't have plans to change that soon, I'm closing this issue. |
🔖 Feature description
A github action workflow that checks pull requests submitted to make sure the changes are not breaking any awesome linting rules.
🎤 Pitch
Knowing that Awesome LInting has good rules that makes an Awesome Listing Repos, free from errors, repeated links, lists that doesnt have comma's, wrong use of full stops and more.
All this get handled by the Awesome linting workflow checks.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: