Downloading a repo either in zip or tar.gz format sets all files date with download date.
How can we preserve last modification date of these files by downloading and not cloning?
Hi Tanguy
The contents of the file will have their date modified attribute set according to the last performed commit against the repository.
In addition, are you referring to Bitbucket Cloud or Server?
Hi Rodrigo,
I'm referring to Bitbucket Server.
When we download, we get all files with same date. With the current date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Tanguy
What Bitbucket version are you running?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Tanguy
I've performed a test on my local instance using Bitbucket v 5.7.1 version and it seems that this is the expected behaviour:
The downloaded file will have the Date Modified attribute set to the day that the file was downloaded, and the contents of the file will have their date modified attribute set according to the last performed commit against the repository.
Regards!
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rodrigo
I've tested on windows and on linux, when files are extracted, OS gives them date of download and not date of "last modified".
Tanguy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Tanguy.
Can you share a screenshot showing all files with the same date as you've mentioned?
Best
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tanguy! Thanks for the screenshots sent.
As I've mentioned before, after extracting the files from the zip file, their date modified attribute will be set according to the last performed commit against the repository.
Take a look at my example on the screenshot attached. On my repo, the last commit against the repo was on Abr 5. This is the expected behaviour.
In your case, the last committed date against the repo was made on Feb 7th.
Regards
Rodrigo!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Rodrigo. Our problem is that we want original 'last modification date' of files and not the date of commit which here is the last commit date.
This might be internal to git? Any idea on how we could retrieve those original modification dates?
Kind regards,
Tanguy!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>This is the expected behaviour.
Why?? What is the sane reason for THIS being the expected behavior?
If I have made a change to just one file out of a hundred, commit that change, and then download a zip of the repo; how do I benefit from not knowing which of the 100 files within needs to actually be extracted according to its' true mod date?
The other 99 files were not modified. Why was it deemed correct behavior to change the mod date of those files? It's a lie! :-]
Is this a limitation of the git specification? Some third-party software you're using?
Not angry. Just amazed, very curious and unable to write my parser.
Also sorry about the 5 year delay...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.