we have disabled force push completely for now to all of the stash repositories.
Hence for private branches folks are deleting the branch and repushing it.
so if they are working on the workspace --> deleted the branch --> pushed the branch to stash
In the web UI if they were on the branch commits page then developer gets a 404 not found.
But then you navigate out of the page and then back via branches then the UI works as expected.
The request is to see if it is possible to notice if the branch got deleted \ newly created and then navigate appropriately to either the base branch or then to the newly pushed branch with the same name.
it is a low priority but good to have feature
So i have the update and way to replicate this scenario.
1 create a branch and checkin to the branch
2 navigate to the branches and select this branch.
3 create a pull request and merge to master select "<input id="delete-branch-checkbox" class="checkbox" style="margin-right: 5px; white-space: nowrap;" type="checkbox" name="delete-branch-checkbox"/> <label style="color: #666666; font-family: Arial, sans-serif; font-size: 14px; line-height: 31px; white-space: nowrap; background-color: #f5f5f5;" for="delete-branch-checkbox">Delete source branch after merging"</label>
4. then click again on the branches and i see
Use the links at the top to get back.
My sincere apologies, you've actually found a bug (apparently it was noticed by someone else, but this is the first I've heard of it). Please watch the following for updates.
It issue is caused by having a 'sticky' branch in the browser so that as you click around our different tabs the same branch is selected. When you merge that pull request the branch is deleted but _your_ browser is still trying to select it. It won't affect other users. You can work around that for now by closing the tab and re-opening Stash again.
Sorry about that.
If the branch has been created again with the exact same name then clicking on the branch link should work as expected. There isn't an internal ID for the branches, it's just using the branch name in the URL.
I'll pass on your suggestion to the team, although I don't think we'll change the error page as it might be just as strange to be redirected to the base branch. Thanks though.
just to clarify so we are on the same page,
The suggestion was to either
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs