chore: mirror commits from bazel-examples to downstreams #394
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.
Note, I put deploy public keys into each of the downstream repos, the private keys are stored in GHA secrets in this repo.
NB: this assumes that the push is a fast-forward, meaning we prevent commits to those two downstream repos directly. If it's not a fast-forward, this new GHA workflow will fail on the
git push
step.@gregmagolan are you okay with making any GHA or CCI edits to this repo and then letting the automation push them? If not I'll have to do something fancier here to rewrite commits on top of the history of the target repo, essentially a rebase.
Changes are visible to end-users: no
Test plan
Will run the new workflow manually at first.