search

PCMDI / mip-cmor-tables

JSON tables for CMOR3 to create Model Intercomparison Project (MIP) datasets
Creative Commons Attribution 4.0 International
2 stars 4 forks source link

Automated versioning on checksum mismatch. #32

Closed wolfiex closed 10 months ago

wolfiex commented 10 months ago

Using a files checksum and commit history, we automatically update the relevant version_metadata fields and re-commit.

wolfiex commented 10 months ago

Commits now retain the push date and part of the original message when republished.

durack1 commented 10 months ago

Commits now retain the push date and part of the original message when republished.

If retrospectively you wanted to update a commit/tag with a date/time etc I have a script in https://github.com/WCRP-CMIP/CMIP6_CVs/blob/master/src/cleanupTags.py that does exactly that. I used it to retag once we had a better versioning notation to use

wolfiex commented 10 months ago

Commits now retain the push date and part of the original message when republished.

If retrospectively you wanted to update a commit/tag with a date/time etc I have a script in https://github.com/WCRP-CMIP/CMIP6_CVs/blob/master/src/cleanupTags.py that does exactly that. I used it to retag once we had a better versioning notation to use

This is less of an issue now, since I am just tagging the new (updated version metadata) commits using the previous ones.

I just wanted something more informative than "Version Metadata Automatically Updated + Checksum Recalculated' or something of the like. This should be even less of an issue when files are updated individually, rather than in batch,