keep_files=true does not work when force_orphan=true

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 gh-pages were not kept.

The corresponding commit is https://github.com/EpistasisLab/penn-ml-benchmarks/pull/93/commits/67f34beaff65ec640e1c3379f959c71986a36c7, whose actions log is here.

What I was hoping was to keep the existing files, add changes, then deploy to gh-pages as a single commit. If this is not possible, perhaps a warning would be helpful for users who expected the two options to work together?

[peaceiris]

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

[ElliotSilver]

We have similar need. Our output is generated by running the master branch through a build process. We want to publish current content, as well as milestone (“v1.0”) content. Regular commits should trigger publication to /current, tagging should trigger publication to /{tag}. For the “current” directory, the content of that directory on the gh_pages branch should be replaced each time with the latest build. However, we don’t want to touch out anything on that branch in a milestone directory, or in the root directory.

• /
  • current <- only directory updated on a regular commit
  • v1.0 <- directory created when master branch is tagged “v1.0” and not modified after
  • v1.1 <- directory created when master branch is tagged “v1.1” and not modified after

This may be related to #273, although each build only contains the content for the in-process build, not the other milestone content.