Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-11520

Ability to make a fork replace the upstream repository

    XMLWordPrintable

Details

    • 4
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Summary

      There is need for the possibility to change a forked repository to become the upstream repository, and all the internal references to the old upstream to points to the new upstream.

      Use Case

      For example, there is an upstream repository (upstream.repo), and with multiple forks, there is a need to rename this upstream repository to ‘upstream.old_repo’, and then rename one of the forked repository to (upstream.repo) the original name of the old upstream repository. By doing this, the forked repository now becomes the new upstream repository.

      To enable all references from CI/CD tools referencing the previous upstream to remain consistent with the new upstream, the internal references of the previous upstream should now be the same for the new upstream.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            voseghale VICTOR-OSEGHALE
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: