This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Make the submodule regression check more robust #7068
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
Previously, the git submodule regression check was based on the commit timestamp alone. There are cases where a pull request was branched off an old version of the base branch that would trigger this check, even though the submodule itself was not changed. Now, if the timestamp-based check detects the submodule is out-of-date, the branch's diff is checked as well to see if the submodule was modified.
Consensus Changes
API Changes
Documentation Additions