We are currently relying on issue template to make sure that our source data is up to date when a build is initiated. But even with issue template and additional log information from GitHub Actions, the source data versioning can be difficult to track down for a particular build. For some of our other data products such as FacDB, it is now best practice to keep track of input versioning using a YAML file. It should be a good improvement to implement similar mechanism for DevDB to ensure source data version control.
We are currently relying on issue template to make sure that our source data is up to date when a build is initiated. But even with issue template and additional log information from GitHub Actions, the source data versioning can be difficult to track down for a particular build. For some of our other data products such as FacDB, it is now best practice to keep track of input versioning using a YAML file. It should be a good improvement to implement similar mechanism for DevDB to ensure source data version control.