chore: debug for deep-preserve logic #5921
Draft
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.
The following problem has been observed in googleapis/java-bigquerystorage@96aa207
"/google-cloud..."
only preventdeep-remove
from affecting these folders"/owl-bot-staging/.*"
only preventdeep-copy
from skipping these files.In other words,
/google.*
basically prevents the matching files from being removed when cleaning up the repository. Later, when bringing the new generated files they may still be overridden if we don't have a similar pattern starting with/owl-bot-staging/v.*/...
(that's thedeep-copy
part).Using this debug branch we got:
Additionally, some manual testing confirmed the
deep-preserve
needs a different pattern starting withowl-bot-staging
in order to prevent replacements: