Skip to content
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

Confirm nothing breaks after rules_docker incompatible change #291

Conversation

alex1545
Copy link
Contributor

rules_docker address this incompatible Bazel change in this PR.
This PR is the verify we don't break things in this project.

@alex1545
Copy link
Contributor Author

This PR will need to be merged after our rules_docker PR is merged.

Copy link

@nlopezgi nlopezgi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sharifelgamal
Copy link
Contributor

The current test error was fixed by something that was merged to master after this PR was created. Can you rebase so I can rerun the tests?

@alex1545 alex1545 force-pushed the rules_docker-incompatible-change branch from a7bf90c to 96901b9 Compare April 16, 2019 14:50
@alex1545
Copy link
Contributor Author

Can you please try again?

@xingao267
Copy link
Contributor

This is no longer needed after #314

@xingao267 xingao267 closed this May 10, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants