This PR clears out the js/ and css/ folders during the Main branch preparations to prevent excess app.[hash].js and app.[hash].css file creations leftover from previous builds.
How to test
This change to a GitHub Actions Workflow has been tested in a forked repo:
This repo has a gh-pages branch just like the original where its js/ and css/ folders have been cleared of all previous versions upon running the modified.github/workflows/gh-pages.yml Workflow by making an arbitrary change to App.vue:
Hypothetically, you could fork this repo and run the build action or make an arbitrary change to a .vue file and watch the build process clear out those folders.
Resolves #77
This PR clears out the
js/andcss/folders during the Main branch preparations to prevent excessapp.[hash].jsandapp.[hash].cssfile creations leftover from previous builds.How to test
This change to a GitHub Actions Workflow has been tested in a forked repo:
Forked repo: https://github.com/quamsta/brand-icon-browser
Forked
gh-pages.yml: https://github.com/quamsta/brand-icon-browser/blob/main/.github/workflows/gh-pages.ymlThis repo has a
gh-pagesbranch just like the original where itsjs/andcss/folders have been cleared of all previous versions upon running the modified.github/workflows/gh-pages.ymlWorkflow by making an arbitrary change toApp.vue:https://github.com/quamsta/brand-icon-browser/tree/gh-pages/js https://github.com/quamsta/brand-icon-browser/tree/gh-pages/css
Compare to the original repo's folders which have a plethora of leftover build artifacts:
https://github.com/uiowa/brand-icon-browser/tree/gh-pages/js https://github.com/uiowa/brand-icon-browser/tree/gh-pages/css
Hypothetically, you could fork this repo and run the build action or make an arbitrary change to a
.vuefile and watch the build process clear out those folders.