nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

strange delete branches on push

antonio molinari

every time a try to push from sourcetree, the push window shows me a branch named "forces", and for default ALWAYS that branch, and don't know who created (maybe a console typing error?).

How can i remove tedinitely that branch "forces", and restore the correct "matching" between local and remote branches so when i open the push window it shows me correctly

master --> master
stable --> stable

AND NOT

master --> foces
stable --> forces

Thank you very much :-)

Accepted answers

antonio molinari

tried all those solutions: the only was i solved with was to re-clone the repo ...

All comments

antonio molinari

i attach the images (it was not possible on original posting window)

antonio molinari

i attach images, it was not possible on the original posting window

stevestreeting

Click the 'Fetch' button on the toolbar, and check the prune option before clicking OK. This will delete any remote branches that your local repo has a record of but which no longer exist on the remote.

To change how SourceTree defaults the Push dialog, check out the options in Preferences > Git > Push branches.

antonio molinari

seems not working, done what you said, still see that strange branch: is there a way to delete that sort of branches list cache ?

stevestreeting

Fetch with prune does delete the local cache of the branches that are on the remote. If it hasn't gotten rid of this branch, it means that it still exists on the remote. If you want to delete it from the remote, you can do so by right-clicking the remote branch in the sidebar (expand the remote entry to see the remote branches, then right-click on it and select delete). Note that this will delete the branch on the remote, not just your own record of it.

antonio molinari

tried all those solutions: the only was i solved with was to re-clone the repo ...

antonio molinari

tried all those solutions: the only was i solved with was to re-clone the repo ...

stevestreeting

Glad you got it sorted out, I don't know how your repo got into this situation since a Fetch with Prune should have had the same effect.