CODEWITHSUNDEEP
bitbucket-cloudsemantic-release
Sammy
Sammy

Reputation: 3697

Avoiding 2nd semantic-release Commit on Bitbucket Cloud

I'm using Bitbucket Cloud and everything works wonderfully using pipelines, except I always get an extra commit after my release/tag commit, as follows:

Notes added by 'git notes add' -- author: semantic-release-bot

Is there any way to avoid this?

Here's my config:

    "release": {
        "plugins": [
            "@semantic-release/commit-analyzer",
            [
                "@semantic-release/changelog",
                {
                    "changelogFile": "CHANGELOG.md"
                }
            ],
            [
                "@semantic-release/npm",
                {
                    "npmPublish": false
                }
            ],
            [
                "@semantic-release/git",
                {
                    "assets": ["CHANGELOG.md"]
                }
            ]
        ]
    },

Upvotes: 0

Views: 401

Answers (1)

Howard Panton
Howard Panton

Reputation: 267

@Sammy - Have you tried to set the message for the commit? Bitbucket recommends using [skip ci] in pipelines

      {
        "path": "@semantic-release/git",
        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
      }

Upvotes: 1

Related Questions