You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
b. click on target branch and get previously created branch name, click on link and get 404 not found page.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.