-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
ci: Fix it + Lint changes #8
Conversation
2d83afc
to
939f367
Compare
ci: Push event only on main style: Remove duplicates, fix broken links.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Two optional suggestions.
Co-authored-by: sobolevn <[email protected]>
Co-authored-by: sobolevn <[email protected]>
probably need to set |
I thought about this, we already allowed some status codes there but 403 felt like a legit code to not allow, but in this case its rather annoying, I can add 403 if you are ok though |
@Alc-Alc maybe awesome-bot allows scoping where the 403 is allowed from |
awesome-lint