Repository navigation
Release v1.3.2: run the pre-push gates on a local checkout on a network share - #21
Merged
Merged
Conversation
…a network share Refs #20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Refs #20
What changes
AISDLC_GATES_LOCAL_CHECKOUT=1forces it, and=0turns it off. Other repositories run the gates in place, as before.//host/sharecounts as a network path.Measured
A push of about 930 files on a network share took 1,425 seconds in the gates. The new hook on the same repository took 15 seconds.
Checks
The pre-flight passes: gates, tests and the secret scan. One gitleaks baseline test failed once on a missing temp file. It passed 3 out of 3 times on its own, and this change does not touch it.