Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

disable "git notes add" behaviour for semantic-release integration


I receive an extra "git notes" commit "Notes added by 'git notes add'" after main branch merge with semantic release integration. This behaviour is reproducible in bitbucket only and visible only in bitbucket UI.


The problem is similar to this one:




2 answers

@Oleksandr Kulbidawere you able to resolve this?

nope, but you can run after each pipeline 😀 

git push origin :refs/notes/semantic-release
0 votes
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 21, 2021

Hi @Oleksandr Kulbida

Welcome to the community.

If you're comfortable sharing your repository URL, may I kindly ask if you could provide it here so that I can check?
You can mask your repository URL by providing only the first and last characters of your workspace and repository name. (For example:*******e/r**o/)

Otherwise, I'll create a support ticket on your behalf.

Mark C

Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 25, 2021

Hi @Oleksandr Kulbida

Thanks for providing your repository URL.

I went ahead and created a support request on your behalf to further investigate the issue.

You should be able to receive an email by now about that support ticket.

Mark C

Like Oleksandr Kulbida likes this

Any updates so far? Running into the same problem. 

I have as workaround an extra step like:


`git push origin :refs/notes/semantic-release`

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events