如何确保CircleCi忽略由CircleCi本身引起的推送？

Question

当代码被推送到master时,CircleCi会运行,但是CircleCi会在调用的运行脚本中推送自己Version Package Bump.所以在第一次构建之后,运行第二次.但它失败了消息:

在分支主数据上您的分支是最新的'origin/master'.无需提交,工作目录清除退出代码1

如何确保CircleCi不会因自身引起的推动而再次启动？

jobs:
  build:
    docker:
      - image: circleci/node:8.10.0
    branches:
      only:
        - master
    steps:
      - add_ssh_keys
      - checkout
      - run:
          name: Keyscan DreamHost (HACK)
          command: ssh-keyscan -H HOST >> ~/.ssh/known_hosts
      - run:
          name: Install Dependencies
          command: npm install
      - run:
          name: Build App
          command: npm run build
      - run:
          name: Verion Package Bump
          command: |
            git config user.name "circleci"
            git config user.email "EMAIL"
            git add .
            git commit -m "[ci] Generated Build"
            npm version patch -m "[ci] Bumped version number to %s"
            git push origin master
            git push --tags
      - deploy:
          name: Publish to DreamHost
          command: scp -r build/* HOST:./DIRECTORY/

即使我将它包装在条件中,我仍然会看到相同的错误,并且构建会发生两次:

if ! git diff-index --quiet HEAD --; then
    git config user.name "circleci"
    git config user.email "EMAIL"
    git add .
    git commit -m "[ci] Generated Build"
    npm version patch -m "[ci] Bumped version number to %s"
    git push origin master
    git push --tags
fi

Answer 1

在提交的消息中的任何位置添加[ci skip]或[skip ci]标记.

请参阅https://circleci.com/docs/2.0/skip-build/

替换你的

git commit -m "[ci] Generated Build"

同

git commit -m "[ci skip] Generated Build"

要么

git commit -m "Generated Build [skip ci]"