Feat: Add destination_files to Push Workflow #81
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.
Pull request
Adding the destination_files option to the push workflow so that we can have files in the
destination repo that are not overwritten when a push from the SoT happens
Related issue
#80
Motivation and context
In our destination repo, we want to have certain files that are only contained in it and not overwritten when pushed to. Specifically we have different github actions in the destination repo vs the SoT repo and don't want them overwritten.
Solution
add destination_files = glob(PR_INCLUDE, exclude = PR_EXCLUDE), to the push workflow
How has this been tested
I used a custom
copy.bara.sky
file and ran it locally and verified that destination files were not overwrittenTypes of changes
Checklist