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

changelog: accept tags in ranges as well as numeric offsets

    XMLWordPrintable

Details

    • 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

      Someone has the question 'what has changed since the last release'?

      You can get a list of changes, like this:

      bitbucket.org/aolserver/aolserver/changesets/

      By default it doesn't show very many, but after clicking 'more' a couple of times, you get to here:

      bitbucket.org/aolserver/aolserver/changesets/1/60/

      The tag aolserver-4.5.0 is about 3/4 down the page.

      What I would like is the ability to pass the questioner a link like this:

      bitbucket.org/aolserver/aolserver/changesets/tip/aolserver-4.5.0/

      To show exactly what has changed during the period of interest.

      At the moment, it seems like I would have to count down (or backwards, up) the page to figure out the offset.

      In addition, if it accepts tags then it should also accept ids and hashes. Unfortunately, I think this clashes with your current syntax where a numeric ID, such as 1491 in the case above, would be confused as an offset, and 1491 changesets on one page is waaay too many.

      So how about this additional syntax:

      bitbucket.org/aolserver/aolserver/changesets/tip:1491/

      ie. if the single changeset specification contains a colon, then it is treated as the '-r' flag is by hg itself.

      In fact, you might want to drop the existing URL syntax altogether. That is, when the user clicks 'more', instead of increasing the offset by 20, decrement the id by 20 and by default construct URLs like the above.

      Attachments

        Activity

          People

            18103154f924 jespern
            legacy-bitbucket-user Legacy Bitbucket Cloud User (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: