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

Ability to retain experimental branches without cluttering up the branches view for everyone

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      I work at a company and I work on product features, coding. There are quite a few times where I'm doing some R&D and putting together a few branches for the same feature but using different approaches. My best practice is to push branches up to the server as soon as possible (so that they are not only accessible to others but also backed up). The thing is ... many times, once we've picked the right approach, I still want to keep the other branches as they've got some valuable techniques or approaches that might come in useful at a later date.

      The problem is I don't want these branches cluttering up everyone's view of our "active" code, I'd rather have it categorised in a way that allows others to filter them out (by default most likely). A "published" flag akin to a blog post draft might work.

      BBS-45402

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            rchia Ronald C.
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: