Open oesteban opened 4 years ago
if you do not expect all files to change with every commit, and do not want to refetch all of them upon each upgrade -- might be overkill. But if that is ok, then might be better to may be use git describe
(well, git describe --tags
since I guess releases are done via github and release tags aren't annotated) version for a given commit? then it would be a clear version for releases and then smth like 1.2.1-4-g350b8b9
if somehow current development version was used? then besides the commit hexsha (350b8b9) you would get the release as well
This is readily doable on DataLad distributions, but would be trivial for S3 (download) distributions with templateflow/templateflow#91.
As commented by @yarikoptic in https://github.com/poldracklab/fmriprep/pull/1802#issuecomment-538398376, it would be great to implement in the client some utility to keep track of the exact template used in an analysis.
I guess that the actual git commit of the templateflow/templateflow repo should suffice? WDYT?