0

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"]
                }
            ]
        ]
    },
Sammy
  • 3,395
  • 7
  • 49
  • 95

1 Answers1

1

@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}"
      }
Howard Panton
  • 247
  • 4
  • 6
  • Thanks but it turned out to simply be Bitbucket’s interpretation of Git Notes that’s lacking, and so makes them appear as extra commits. – Sammy Oct 07 '21 at 10:13