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

version number #154

Closed
akhanf opened this issue Jan 12, 2022 · 1 comment
Closed

version number #154

akhanf opened this issue Jan 12, 2022 · 1 comment
Labels
maintenance Updates or improvements that do not change functionality of the code

Comments

@akhanf
Copy link
Member

akhanf commented Jan 12, 2022

The Issue #67 also mentioned we should add a version number somewhere to usage, and perhaps also to outputs themselves -- maybe in a dataset_description.json file that is produced?

@akhanf akhanf added the maintenance Updates or improvements that do not change functionality of the code label Feb 10, 2022
@akhanf
Copy link
Member Author

akhanf commented Sep 8, 2022

With #210, we now have a CLI option, e.g. hippunfold --version that returns the version number.
This number exists directly in the config file (in the argparser), and is updated with github actions. Since it is in the config, you will get the version number in your dataset (in the output config folder) too.

At some point we can also introduce writing the dataset_description.json (which now also has the version number)

@akhanf akhanf closed this as completed Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Updates or improvements that do not change functionality of the code
Projects
None yet
Development

No branches or pull requests

1 participant