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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,338
Community Members
 
Community Events
176
Community Groups

Error: When renaming remote branch name, old name still occur on BB with dead links 404

1. Create pull request.

2. Rename remote branch using
```bash

$ git push origin :fealure/CPT-270-old_name feature/CPT-270-new_name
Total 0 (delta 0), reused 0 (delta 0)
To bitbucket.org:user_name/project_name.git
- [deleted] fealure/CPT-270-old_name
* [new branch] feature/CPT-270-new_name -> feature/CPT-270-new_name

```

3. Go to BB on previously created pull request and:

a. see old branch name in source side

image.pngimage.pngimage.pngb. click on target branch and get previously created branch name, click on link and get 404 not found page.

 

 

1 answer

0 votes

Hi @asi_lh,

There is no way to directly rename a branch in a remote repository. What the push command is doing is deleting the old branch and creating a new one, so for the remote repo, this is a new, different branch.

That being said, we could offer the option to change the source branch in the pull request, which is something that doesn't work at the moment.

We have a bug report in our issue tracker about this that you can vote for and add yourself as a watcher if you'd like to get notified on updates:

In the meantime, the way to work around this would be by declining this PR and creating a new one with the new branch as a source.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events