Add exclude option

[YuyaAizawa]

Add exclude input parameter for tar option --exclude.

Assuming a project using npm, we do not want to include node_modules files in the tar.
This change make it possible by the followings

- name: Install dependencies
  run: npm ci

- name: Build
  run: npm run build

- name: Upload artifacts
  uses: actions/upload-pages-artifact
  with:
    path: .
    exclude: node_modules

[YuyaAizawa]

I came up with a simple workaround after submitting this pull request. It worked as expected, although it was a little weird to have it be like an injection...

- uses: actions/upload-pages-artifact@v1
  with:
    path: '. --exclude=node_modules'

[yoannchaudet]

Path escaping has been fixed in #19 so your workaround should not work anymore.

Why are you using . as your path? Most (all?) static site generators place static (and built) assets in a dedicated folder. Otherwise you would also include all your source files and package.json in your site...

What does your build script do now?

[YuyaAizawa]

I planed that my site generator places static assets in root folder for simplification. I assumed that few folders makes it easy for beginner developers and it would not be a problem to publish files that are not needed as long as they are not too large.

But I have now reconsidered that the files to be made public should be explicit and separated in a single folder. The build script is also set to path: public/ now. Thank you.