Yeah we're running into this now, adds drag to our process. I think we may just recreate the repo as a work around.

+1 that the users should be able to fork a repository and not have to contribute back to the parent repository.

As a work-for-hire tech company, we use forking from template repos to get new projects up and running quickly. I feel that this qualifies as a legitimate use of the repository forking procedure

+1 the user should have the ability to change the default target, as the forked repository may only contribute back 1 or 2 times a year.

+1 and I don’t understand why this hasn’t been fixed in the 4 years this has been reported. Defaulting to the origin is non-intuitive and (in my opinion) a bug. Either change the default to the forked repository or give users the ability to change the default target.

I wouldn't even classify this as an enhancement, its a BUG!!! (default git behavior which is not working as expected... it's not something which is 'new' to the git ecosystem). BB has all the information backend, just literally need to have the option frontend? Surely a simply GUI fix?

Don’t mistake silence for complacency nor acceptance.

awilkes There has been no discussion from Bitbucket side. Users have shared their needs, that have not been addressed.

Have you expected a discussion whether we want a dropdown or a textbox?

We need the feature, it’s not implemented, we hoped Bitbucket team can deliver.

awilkes , what else are we supposed to be discussing here?

Suspecting that the only reason there’s been little discussion recently, is because people who read this thread feel like the Bitbucket team aren’t taking them seriously.

Hi everyone,

Given the relative lack of discussion on this issue in recent years, and since the team is currently focused on higher priority items, I am closing this issue to indicate that we don't plan to address this in the near future.

Thanks,
Alastair
Bitbucket PM