A Github Action that overwrites your Github Pages branch with the content of current workdir, thus deploy/publish without polluting your repo history.

Github Page Overwriter is:

• the simplest possible Github Page publisher, because it requires no configuration
• the most lightweight Github Page publisher (therefore the fastest possible - typically around 2 seconds), because its implementation requires no runtime dependency other than git itself.
• the cleanest possible Github Page publisher, because it is designed to leave no extra commits in your repo history.

1. Github Page Overwriter requires no mandatory configuration. You simply add it as one extra step into your own github action.

   name: Your github action
   
   on:
     push:
       branches:
         # NOTE: You may want to limit the trigger branch to be "main" or "master" etc.
         - *
   
   jobs:
     publish:
       runs-on: ubuntu-latest
       steps:
         - name: Check out
           uses: actions/checkout@v2
   
         - name: Generate your content
           run: echo "Optional placeholder. Put your project's static website generator command here."
   
         - name: Publish current workdir (which contains generated content) to GitHub Pages
           uses: rayluo/github-pages-overwriter@v1.1
   
           with:
   
             # Optional. Default value "." means the root directory of your project will be published.
             # You can use whatever directory your project uses, for example "wwwroot".
             # Such a directory does *not* have to already exist in your repo,
             # it could be an output directory created dynamically by your static website builder.
             source-directory: .
   
             # Optional. Default value "gh_pages".
             # It specifies the temporary branch which hosts the static website.
             # Each build will OVERWRITE this branch.
             target-branch: gh_pages

2. In your Github Pages setting, choose your publish source like this:

   Github Page Overwriter settings	Github Pages settings
   source-directory can be any directory you choose	Always choose folder / (root) for your publishing source, regardless of what source-directory is.
   target-branch can be any branch that match the setting on the right	Choose any branch that matches the target-branch setting on the left

Behind its simplest usage pattern, Github Page Ovewriter is based on a sophisticated Version Control System philosophy:

1. Your repo stores the history of your project's source code and assets.
2. Any artifact that can be built from a snapshot of those source code and assets, should not be stored inside the repo history.

Yet, in order to take advantage of the free hosting service of Github Pages, those artifacts would need to be stored inside a repo, thus violating tenet 2 above. Some publisher actions work around this by pushing the artifacts into a dummy repo which is only used for hosting the static website. That's fine, but you'd need to provision a personal access token (PAT) for it, and then configure your Github Action to use the PAT.

Github Page Overwriter takes a simpler approach. The artifact will be forcefully pushed into - thus overwrite - the gh-pages branch inside your same main repo. This way, that publish commit would be overwritten each time, thus won't become part of your repo's long term history.

1. For example, your repo starts like this when you are ready for the first publish:

    D---E---F  main
   

2. Trigger this action once, your repo would look like:

              A  gh-pages
             /
    D---E---F  main
   

3. Later you added more work into your repo, and now ready for a new publish.

              A  gh-pages
             /
    D---E---F---G---H  main
   

4. Trigger this action one more time, your repo would look like:

                      A'  gh-pages
                     /
    D---E---F---G---H  main