Skip to content
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
merged 1 commit into from
Apr 4, 2019

Conversation

knmorgan
Copy link
Contributor

@knmorgan knmorgan commented Apr 4, 2019

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

  • Consensus Changes

API Changes

  • API Changes

Documentation Additions

  • Documentation Additions

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.
@knmorgan knmorgan requested a review from larryk85 April 4, 2019 20:39
@heifner heifner merged commit b9b34fb into develop Apr 4, 2019
@heifner heifner deleted the git-submodule-check-update branch April 4, 2019 21:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants