docs: fix

README.md

@@ -28,6 +28,7 @@ Table of Contents
     - [⭐️ `PERSONAL_TOKEN`](#%EF%B8%8F-personal_token)
     - [⭐️ `GITHUB_TOKEN`](#%EF%B8%8F-github_token)
     - [⭐️ Suppressing empty commits](#%EF%B8%8F-suppressing-empty-commits)
+    - [⭐️ Keeping existing files](#%EF%B8%8F-keeping-existing-files)
 - [Tips and FAQ](#tips-and-faq)
   - [How to add `CNAME`](#how-to-add-cname)
   - [Deployment completed but you cannot read](#deployment-completed-but-you-cannot-read)
@@ -189,7 +190,7 @@ By default, a commit will always be generated and pushed to the `PUBLISH_BRANCH`
 For example:
 
 ```yaml
-- name: deploy
+- name: Deploy
   uses: peaceiris/actions-gh-pages@v2.3.2
   env:
     ACTIONS_DEPLOY_KEY: ${{ secrets.ACTIONS_DEPLOY_KEY }}
@@ -206,7 +207,7 @@ By default, existing files in the publish branch are removed before adding the o
 For example:
 
 ```yaml
-- name: deploy
+- name: Deploy
   uses: peaceiris/actions-gh-pages@v2.3.2
   env:
     ACTIONS_DEPLOY_KEY: ${{ secrets.ACTIONS_DEPLOY_KEY }}
@@ -217,6 +218,7 @@ For example:
 ```
 
 
+
 ## Tips and FAQ
 
 ### How to add `CNAME`

entrypoint.sh

@@ -62,8 +62,9 @@ local_dir="${HOME}/$(tr -cd 'a-f0-9' < /dev/urandom | head -c 32)"
 if git clone --depth=1 --single-branch --branch "${remote_branch}" "${remote_repo}" "${local_dir}"; then
     cd "${local_dir}"
 
-    print_info "Keeping existing files: ${INPUT_KEEPFILES}"
+    if [[ ${INPUT_KEEPFILES} == "true" ]]; then
-    if [[ ${INPUT_KEEPFILES} != "true" ]]; then
+        print_info "Keeping existing files: ${INPUT_KEEPFILES}"
+    else
         git rm -r --ignore-unmatch '*'
     fi