Closed meteorcloudy closed 5 years ago
wait, this patch file was produced with git diff > blah.patch
in the other repo.
If that pattern doesn't work with Bazel it seems like a big problem? I think it's bazel that should be fixed to work with Git-produced diffs maybe?
Thanks, indeed, I tested with diff on adding/deleting one liner file. It does output such format, I'll fix this from Bazel side.
The chuck header format is wrong, which doesn't work with
--incompatible_use_native_patch
in Bazel.Attention Googlers: This repo has its Source of Truth in Piper. After sending a PR, you can follow http://g3doc/third_party/bazel_rules/rules_typescript/README.google.md#merging-changes to get your change merged.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information