[Deploy merge instead delete old files] can i deploy use merge instead removing all old files ?

[dimaslanjaka]

i have a lot nodejs process, and they have separated runner.
i want deploy to my github pages with pull first instead push --force directly. so, my other old files not be deleted after deployed

• ive searched google, no solution

my sample 1 workflow

name: Build

on:
  push:
    branches:
      - compiler # run when this branch pushed

# cancel previous workflows, run only one workflow
concurrency:
  group: build-${{ github.event.push.number || github.event.pull_request.number || github.ref }}
  cancel-in-progress: true

jobs:
  build:
    #if: {{ $false }}
    runs-on: ubuntu-latest
    timeout-minutes: 120
    env:
      NODE_OPTIONS: "--max_old_space_size=8192" #8192 4096 --expose-gc
      GITFLOW: true
    steps:
      - name: Checkout repository and submodules
        uses: actions/checkout@v2
        with:
          submodules: recursive
          token: "${{ secrets.GITHUB_TOKEN }}"
      - name: Setup Node.js 16.x
        uses: actions/setup-node@v1
        with:
          node-version: "16.x"
      - name: Get current date
        id: date
        run: echo "::set-output name=date::$(date +'%Y-%m-%dT%H:%M:%S')"
      - name: Setup GitHub
        run: |
          git config --local user.email "41898282+github-actions[bot]@users.noreply.github.com"
          git config --local user.name "github-actions[bot]"
      - name: Get npm cache directory
        id: npm-cache-dir
        run: echo "::set-output name=dir::$(npm config get cache)"
      - name: Get yarn cache directory path
        id: yarn-cache-dir-path
        run: echo "::set-output name=dir::$(yarn config get cacheFolder)"
      - name: Get Caches
        id: npm-cache # use this to check for `cache-hit` ==> if: steps.npm-cache.outputs.cache-hit != 'true'
        uses: actions/cache@v2
        with:
          path: |
            ${{ steps.npm-cache-dir.outputs.dir }}
            ${{ steps.yarn-cache-dir-path.outputs.dir }}
            ./node_modules
            ~/.npm
            ./tmp
            ./build
            ./packages
            ./databases
          key: ${{ runner.os }}-xnodex-${{ hashFiles('**/.guid') }}
          restore-keys: ${{ runner.os }}-xnodex-
      - run: npm i -g npm hexo-cli gulp-cli typescript ts-node
        # run global install when cache not written
        # if: steps.npm-cache.outputs.cache-hit != 'true'
      #- run: rm -rf node_modules tmp build
        # run if commit contains substring 'clean cache'
        #if: "contains(github.event.head_commit.message, 'clean cache')"
      - run: npm install
      - run: "gulp copy:assets"
      - run: "gulp copy:posts"
      - run: "gulp generate:assets"
      - run: "gulp generate:template"
      - run: "gulp generate:posts"
      - run: "gulp generate:after"
      - run: cp -rf docs/sitemap.html docs/index.html
      - run: cd docs/page && npm install
      - run: cp -rf source/robots.txt docs/robots.txt
      - run: echo www.webmanajemen.com > docs/CNAME
      - name: Deploy 🚀
        #if: ${{ false }}
        #if: steps.hexo-validate.outcome == 'success' && steps.hexo-validate.conclusion == 'success'
        uses: JamesIves/[email protected]
        with:
          branch: master # The branch the action should deploy to.
          folder: docs # The folder the action should deploy.

[JamesIves]

Might be worth checking out the force option that was released in yesterday's update, I think toggling it to false might be helpful.

[dimaslanjaka]

Might be worth checking out the force option that was released in yesterday's update, I think toggling it to false might be helpful.

like this ?

- name: Deploy 🚀
        #if: ${{ false }}
        #if: steps.hexo-validate.outcome == 'success' && steps.hexo-validate.conclusion == 'success'
        uses: JamesIves/[email protected]
        with:
          branch: master # The branch the action should deploy to.
          folder: docs # The folder the action should deploy.
          force: false # merge instead push --force, (keep old / non modified) files?

[JamesIves]

You'd also need to update to the latest version, but yeah.

[dimaslanjaka]

You'd also need to update to the latest version, but yeah.

not working. old files still deleted. this action cannot run on separated workflow yml files. old files (not modified) on existing repo got deleted.

- name: Deploy 🚀
        #if: ${{ false }}
        #if: steps.hexo-validate.outcome == 'success' && steps.hexo-validate.conclusion == 'success'
        uses: JamesIves/[email protected]
        with:
          branch: master # The branch the action should deploy to.
          folder: docs # The folder the action should deploy.
          force: false # merge instead push --force, (keep old / non modified) files?

also this not working

- name: Deploy 🚀
        #if: ${{ false }}
        #if: steps.hexo-validate.outcome == 'success' && steps.hexo-validate.conclusion == 'success'
        uses: JamesIves/[email protected]
        with:
          branch: master # The branch the action should deploy to.
          folder: docs # The folder the action should deploy.
          force: false # merge instead push --force, (keep old / non modified) files?

[dimaslanjaka]

i need action that runs:

git pull # fetch old files from repository
# process files here
git add -A # add modified files
git push origin ${branch-name} # push

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run

.github/workflows/page1.yml 
.github/workflows/page2.yml # the files from page1.yml not restored

[dimaslanjaka]

actually this is for cache strategy, so process won't be repeated for files that are not changed (like articles for example). so the process only runs for files that have been managed or new files (new article). and the old files are left alone because they don't need to be forced (save time)

[dimaslanjaka]

i using this to manage my github page within more than 1000 posts, so i dont need to repeat all file processes

[dimaslanjaka]

nodejs can't process 1000+ files at once. so it must be separated. Therefore, a 'git action deployer' which can be merged with the previous file is needed

[dimaslanjaka]

my full config

name: Build

on:
  push:
    branches:
      - compiler # run when this branch pushed

# cancel previous workflows, run only one workflow
concurrency:
  group: build-${{ github.event.push.number || github.event.pull_request.number || github.ref }}
  #cancel-in-progress: true

jobs:
  build:
    if: {{ $false }}
    runs-on: ubuntu-latest
    timeout-minutes: 120
    env:
      NODE_OPTIONS: "--max_old_space_size=8192" #8192 4096 --expose-gc
      GITFLOW: true
    steps:
      - name: Checkout repository and submodules
        uses: actions/checkout@v2
        with:
          submodules: recursive
          token: "${{ secrets.GITHUB_TOKEN }}"
      - name: Setup Node.js 16.x
        uses: actions/setup-node@v1
        with:
          node-version: "16.x"
      - name: Get current date
        id: date
        run: echo "::set-output name=date::$(date +'%Y-%m-%dT%H:%M:%S')"
      - name: Setup GitHub
        run: |
          git config --local user.email "41898282+github-actions[bot]@users.noreply.github.com"
          git config --local user.name "github-actions[bot]"
      - name: Get npm cache directory
        id: npm-cache-dir
        run: echo "::set-output name=dir::$(npm config get cache)"
      - name: Get yarn cache directory path
        id: yarn-cache-dir-path
        run: echo "::set-output name=dir::$(yarn config get cacheFolder)"
      - name: Get Caches
        id: npm-cache # use this to check for `cache-hit` ==> if: steps.npm-cache.outputs.cache-hit != 'true'
        uses: actions/cache@v2
        with:
          path: |
            ${{ steps.npm-cache-dir.outputs.dir }}
            ${{ steps.yarn-cache-dir-path.outputs.dir }}
            ./node_modules
            ~/.npm
            ./tmp
            ./build
            ./packages
            ./databases
          key: ${{ runner.os }}-xnodex-${{ hashFiles('**/.guid') }}
          restore-keys: ${{ runner.os }}-xnodex-
      - run: npm i -g npm hexo-cli gulp-cli typescript ts-node
        # run global install when cache not written
        # if: steps.npm-cache.outputs.cache-hit != 'true'
      - run: npm install
      - run: gulp clean
        if: "contains(github.event.head_commit.message, 'clean cache')"
      - run: "gulp copy:assets"
      - run: "gulp copy:posts"
      - run: "gulp generate:assets"
      - run: "gulp generate:template"
      - run: "gulp generate:posts"
      - run: "gulp generate:after"
      #- run: cp -rf docs/sitemap.html docs/index.html
      - run: cd docs/page && npm install
      - run: cp -rf source/robots.txt docs/robots.txt
      #- run: cp -rf .gitignore docs/.gitignore
      - run: cp -rf README.md docs/readme.md
      - run: echo www.webmanajemen.com > docs/CNAME
      - name: Deploy 🚀
        #if: ${{ false }}
        #if: steps.hexo-validate.outcome == 'success' && steps.hexo-validate.conclusion == 'success'
        uses: JamesIves/[email protected]
        with:
          branch: master # The branch the action should deploy to.
          folder: docs # The folder the action should deploy.
          force: false # merge instead push --force, (keep old / non modified) files?

[dimaslanjaka]

so, now i just manually copy the public files to github page branch

[dimaslanjaka]

look. index.html got removed, iam not modifying index.html at all. leaving only readme.md alone

[dimaslanjaka]

This work, but only for local process. not working when i run this on 'github action'.

https://github.com/dimaslanjaka/dimaslanjaka.github.io/blob/compiler/src/gulp/tasks/deploy.ts

[dimaslanjaka]

I can't write articles directly from github when I'm not in front of the computer, because not deployed by github action

[dimaslanjaka]

I've confirmed, JamesIves/[email protected] still deletes old files and pushes them right away

[dimaslanjaka]

SOLUTION: cache the public directory to keep old processed files

- name: Get Caches
    id: npm-cache # use this to check for `cache-hit` ==> if: steps.npm-cache.outputs.cache-hit != 'true'
    uses: actions/cache@v2
    with:
      path: |
        ${{ steps.npm-cache-dir.outputs.dir }}
        ${{ steps.yarn-cache-dir-path.outputs.dir }}
        ./node_modules
        ~/.npm
        ./tmp
        ./build
        ./packages
        ./databases
        ./docs
      key: ${{ runner.os }}-xnodex-${{ hashFiles('**/.guid') }}
      restore-keys: ${{ runner.os }}-xnodex-
- name: Deploy 🚀
    #if: ${{ false }}
    #if: steps.hexo-validate.outcome == 'success' && steps.hexo-validate.conclusion == 'success'
    uses: JamesIves/[email protected]
    with:
      branch: master # The branch the action should deploy to.
      folder: docs # The folder the action should deploy.
      force: false # merge instead push --force, (keep old / non modified) files?