File name when downloading a tag

Issue #3486 wontfix
Jérôme Berger
created an issue

When downloading a tag as a .tar.gz, .tar.bz2 or .zip archive, the file is named: "{{{user-repository-hash.}}}", same as when downloading a snapshot referred by hash. It would be nice if the archive (and the included folder) was named "{{{user-repository-tag.}}}".

For example, when downloading the file is named "{{{jmb-cseh-ad591c014a9e.tar.gz}}}" but I would prefer to get "{{{jmb-cseh-1.2.0.tar.gz}}}".

Comments (5)

  1. Erik van Zijst staff

    Hi Jérôme,

    What you're describing is how Bitbucket worked up until about a month ago, when we inadvertently changed it (and broke people's scripts that relied on that filename pattern).

    We now find ourselves in a difficult situation. Changing it back will once more break it for people en so for now we're going to stick with what we have. Should we decide to change it again in the future, we'll properly announce it.


  2. Sam Clegg

    Yes, please take the advice of Antonio Cavallo.

    Better still, do it like github does and make it so that filename can be anything you like:<username>/<repository>/get/<tag>/what_ever_you_like.tar.gz

    The contents of the file can either always be <repo>-<tag> or it can be <what_ever_you_like>.

    We rely on having sensible filenames and archive contents in the naclports project ( and this feature of github provides what we need.

    Right now, if a project uses bitbuckets tags for releasing source archives there are several drawbacks. Take for example the eigen project: Their official release source archive is There are 2 major problems with this:

    1) if you download it you end up with a file called "3.2.4.tar.gz" in your downloads directory. This is very unhelpful.

    2) if you extract this archive you see that everything is within a directory called 'eigen-eigen-10219c95fe65'. Again, not very helpful all all. This should simply be "eigen-3.2.4".

    Please please please fix this.

  3. Log in to comment