Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-6851

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

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        1. commit-in-JIRA.jpg
          commit-in-JIRA.jpg
          467 kB
        2. commit-on-BB.jpg
          commit-on-BB.jpg
          537 kB

        Activity

          People

            Unassigned Unassigned
            cdarroch Daz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: