Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting the exact version of a template used #28

Open
oesteban opened this issue Oct 7, 2019 · 2 comments
Open

Reporting the exact version of a template used #28

oesteban opened this issue Oct 7, 2019 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@oesteban
Copy link
Member

oesteban commented Oct 7, 2019

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?

@yarikoptic
Copy link
Contributor

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

@oesteban oesteban changed the title Guaranteeing the exact version of a template used Reporting the exact version of a template used Jul 5, 2021
@oesteban
Copy link
Member Author

oesteban commented Jul 5, 2021

This is readily doable on DataLad distributions, but would be trivial for S3 (download) distributions with templateflow/templateflow#91.

@oesteban oesteban added the enhancement New feature or request label Jul 5, 2021
@oesteban oesteban added this to the 20.0.0 milestone Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants