CI about checka11y.css HOT 5 CLOSED

As for Linting I can make it a separate PR, but I don't think it needs to commit. Linting at CI should be the whole repo, but a git reset in a github action, could equally as well have it check, just the changed files.

from checka11y.css.

Hi. When I get chance, I was going to research how to automatically run the tests in some sort of pipeline, so the PR can't be merged until all tests pass. In terms of linting, I thought this would be more difficult because it will need to do a commit automatically.

But, if you can do this, then that would be super helpful!

from checka11y.css.

Can you expand on

In terms of linting, I thought this would be more difficult because it will need to do a commit automatically.

I'll supply instructions with the PR for adding guards for the primary branch

from checka11y.css.

Linting PR is not merged 😉 feel like re-opening. We just got CI in without linting so-far

from checka11y.css.

Reopening for @Lewiscowles1986 and linting 😉

from checka11y.css.