fix: narrow down Dockerfile drift detection#7391
Merged
Conversation
081c8c0 to
3d1a38e
Compare
3d1a38e to
dfde28a
Compare
pranavjain97
approved these changes
Dec 1, 2025
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.
Using the --ignore-scripts argument will result in a different set of dependencies being installed. For example, some native dependencies won't be installed, so fallbacks will be used. I'm not sure exactly why we're using the argument sometimes and other times we aren't, so in the meantime I'm making sure that we ignore the
yarn.lockdrift when detecting drift in thebitgo/expressDockerfileTICKET: VL-3710