Check non-primitive files match upstream
Before validating changed files, check whether any non-primitive file has been changed. If they have, fail validation immediately with an informative message telling you to update your branch. Without this check, the validator will try to validate those files and fail with non-obvious message about that file being invalid, which is confusing to the user if he didn't even touch that file (it changed upstream).
Showing with 3 additions and 0 deletions