Shohei Ueda

Please check out the following tips first! ## Upload image/movie as githubusercontent I recommend [this approach](https://github.com/peaceiris/actions-gh-pages/issues/748#issuecomment-1127758024) again. ## GitHub Pages does not support files under Git LFS > **Note** >...

Is your Hugo project located in the repository root? Your project seems to have a Hugo project under a sub directory. In this case you can use the `steps.run.working-directory`. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun...

This looks the desired behavior and it means that the current build assets are the same as previous. See also https://github.com/peaceiris/actions-gh-pages/pull/698

> Can I override this behavior and force actions-gh-pages to deploy without checking whether there is diff or not? Something like [git allow empty commit](https://stackoverflow.com/a/61789697/10305444)?! [allow_empty_commit](https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-allow-empty-commits-allow_empty_commit) option is available.

See also the [`keep_files`](https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-keeping-existing-files-keep_files) input option. Anyway, there is no action we should take when the publishing assets are the same as the previous one.

What is your purpose in the setting `destination_dir: docs`? Why don't you deploy the root directory of the `gh-pages` branch? Deploying `/docs` is an old way.

Thank you for the feedback. > I'm using v3, and when I added the `force_orphan: true` option in my deploy step, `keep_files: true` seemed to stop working. Existing files on...

Yes, it looks a practical use case. We need v4.

Anything else confusing users? (option names, documents, and so on.)

Thank you for the work. This pull-request fixes #309