CenterADiv
CenterADiv

Reputation: 81

Prevent trigger recursion when using automatic changelog with standard version in azure pipeline

I generate an changelog based on my commit history using standard-version.
This are my azure pipeline steps to generate the changelog:

 git checkout -b $(Build.SourceBranchName)
    npm run release
    git push --follow-tags origin HEAD:$(Build.SourceBranchName)

The npm run release script does this:

standard-version --skip-commit

It works how it supposed to, the changelog is generated and committed. My problem is that the pipeline reruns when the changelog and the package.json file are commited.I added these files to trigger excludes:

   exclude:
          - CHANGELOG.md
          - README.md
          - package.json
          - package-lock.json

but i wondered if there is a cleaner solution

Upvotes: 0

Views: 178

Answers (0)

Related Questions