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

Commits from other Repos

Tim Cannings
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 13, 2023

I have the odd issue that i seem to have branches from other repos in other repos. At first this appeared in source tree but not on the WebPortal. I assumed sourcetree was having some sort of issue seeing multiple branches and was incorrectly showing them.

However it appears that i am seeing commits and branches that shouldnt be in the a repository as they are from another?

Has anyone had something similar? Probably something we've done although its a strange occurrence as our Repo are separate??

Tim

1 answer

1 vote
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 16, 2023

Hi Tim and welcome to the community!

While it is not common practice, it is possible to add in repo1 a branch that belongs to repo2.

For example, you can add a second remote to a clone of repo1 with

git remote add second_remote git@bitbucket.org:my-workspace/repo2.git

Fetch all references:

git fetch --all

Create in the clone of repo1 a branch that tracks the remote branch feature from repo2

git checkout -b feature --track second_remote/feature

and then push this branch to repo1 with

git push origin feature

where origin is the remote repo1.

You can delete both locally and in the Bitbucket Cloud repo any branches that shouldn't be there. However, I would suggest checking with your team first, in case there was a reason someone pushed this branch to repo1.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events