You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need get all of the counts again without the .css.orig files, and we could update the Google Doc with the new counts, but it seems like we would benefit from having this data on Github so it is more shareable and we can keep track of history – is that something that could be part of this repo?
In order to automate this vs. manually copy/pasting the data as in the GDoc, it could work something like this (starting to test this out in this WIP PR):
Refactor to return an object of the results that can be used in other scripts
Refactor to move the CLI-specific contents to a cli.js
Create a new CLI argument - css-audit ./wp-admin/* --all --generate-report=wp-admin
--generate-report will output the audit results to an .html file inside public/wp-admin.html
Then public/ can be deployed on Github pages. Thoughts?
The text was updated successfully, but these errors were encountered:
We need get all of the counts again without the .css.orig files, and we could update the Google Doc with the new counts, but it seems like we would benefit from having this data on Github so it is more shareable and we can keep track of history – is that something that could be part of this repo?
In order to automate this vs. manually copy/pasting the data as in the GDoc, it could work something like this (starting to test this out in this WIP PR):
css-audit ./wp-admin/* --all --generate-report=wp-admin
--generate-report
will output the audit results to an .html file inside public/wp-admin.htmlThen public/ can be deployed on Github pages. Thoughts?
The text was updated successfully, but these errors were encountered: