Remove CI tests for versioned releases of Bazel and dependencies.#335
Merged
Conversation
swiple-rules-gardener
force-pushed
the
test_274232256
branch
from
October 11, 2019 21:49
9833b9e to
9d3366e
Compare
Unfortunately, the team maintaining this repository does not have the resources to keep the versioned releases up to date. Going forward, the recommended approach for depending on this repository is to select a specific commit and to use the `git_repository` WORKSPACE rule available in `@bazel_tools//tools/build_defs/repo:git.bzl`. RELNOTES: None PiperOrigin-RevId: 274255348
swiple-rules-gardener
force-pushed
the
test_274232256
branch
from
October 11, 2019 21:58
9d3366e to
1e6557b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Remove CI tests for versioned releases of Bazel and dependencies.
Unfortunately, the team maintaining this repository does not have the resources to keep the versioned releases up to date. Going forward, the recommended approach for depending on this repository is to select a specific commit and to use the
git_repositoryWORKSPACE rule available in@bazel_tools//tools/build_defs/repo:git.bzl.