Reindex commit branches when a branch is (forcefully) renamed or deleted (BB-8026)

Chris Darroch avatarChris Darroch created an issue

For example, https://bitbucket.org/atlassian/jira/commits/42afd709b571230cbe9d60fa3a090ac8f840c191?at=atlassian_jira_6_0_OD_10_release_branch -- the commit is present on the "atlassian_jira_6_0_OD_10_release_branch" branch, but the branch shows up as either emtpy or "OD10". This is because before being pushed to the release branch, it had been erroneously pushed to a new branched called "OD10". That branch was deleted shortly afterward, but not before bitbucket had a chance to index and cache it.

Comments (2)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.