-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
create github action workflow for linting html #154
Conversation
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.
I am probably not too knowledgeable about this so excuse the possibly silly question @Roshanjossey :) – should the lint not run through properly on this pull request then? As it seems it failed.
The failing one is the old circle CI linter. The new one doesn't appear to have run here. |
I tried this in my fork before raising a PR here. Roshanjossey#3 Lint action runs there and fails with expected error messages. My theory about it not running here is that there is higher security restriction here to prevent workflows in PRs running |
probably we need some change, maybe close and reopen this PR? reading here I think that would do it |
|
.github/workflows/lint.yml
Outdated
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout code | ||
uses: actions/checkout@v2 |
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.
any reason to not use v3?
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.
No, updated to v3
I changed the settings for including github created actions (somehow thought this would have been default 🤪 ) |
ok sorry @Roshanjossey I got there now 😅 The setting I chose did not include github created actions, I noticed here the following: -- Error: .github#L1 |
now it runs but fails because of the following reasons:
as it's not very many do you want to fix them here? |
use SVG instead of spans to make it semantic
Thank you for following up @sleepypioneer. Ended up fixing #152 too when fixing lint errors |
<div class="animated-icon"><span></span></div> | ||
|
||
<button class="navbar-toggler first-button" type="button" data-toggle="collapse" data-target="#navbar" aria-controls="navbar" aria-expanded="false" aria-label="Toggle navigation"> | ||
<span class="screen-reader-text">Menu</span> |
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.
is this a new thing? Seems like a good thing but I am not very familiar with this code. Not sure if this was related to a failing HTML linter or if seemed appropriate to add this in here?
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.
This is a re-implementation of hamburger button for menu in mobile width that got removed in #138
This has to be handled to pass lint because the empty button and span tags trigger warnings from tidy.
I decided not to revert to old changes and implement it in a different way because this would be a more semantic HTML way to do this.
Also, interestingly, this bug may have been introduced to fix lint errors (as described in #123). So, we're coming full circle.
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.
thanks for clarifying 🙏 I could certainly do with a refresh of the code base!
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 for taking this on @Roshanjossey, awesome improvement
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.
Thanks a bunch, also for all the fixes! :) Let's get this in
address: #142