Closed danielhuppmann closed 4 months ago
The validation can be seen "in action" here
Thanks @phackstock - I prefer to keep the requirements.txt file for now because this is an easy way for new users to quickly see what is required to run this project. We can add it to the Readme instead in a follow-up PR.
This PR adds a test and GitHub Actions workflow to guard against mistakenly adding variables that were marked as being superseded by new variables.
The way that legacy variables are marked in the common-definitions repository is by having an attribute with the legacy project name, currently "navigate" and "engage".
The test workflow checks that all such attributes are not duplicates of variables in the VariableCodeList.