Repository navigation
Reporting the exact version of a template used #28
Description
As commented by @yarikoptic in nipreps/fmriprep#1802 (comment), 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?
Activity
yarikoptic commentedon Oct 8, 2019
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 --tagssince 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 like1.2.1-4-g350b8b9if somehow current development version was used? then besides the commit hexsha (350b8b9) you would get the release as well[-]Guaranteeing the exact version of a template used[/-][+]Reporting the exact version of a template used[/+]oesteban commentedon Jul 5, 2021
This is readily doable on DataLad distributions, but would be trivial for S3 (download) distributions with templateflow/templateflow#91.