Empty commit to retag 2.5.0-palantir.8 as 3.0.0-palantir.26 - #543
Merged
Conversation
|
in the future, would appreciate it if you did not let these merge without passing tests. i know there is no code change, but rather than having issues down the line, we might as well let our testing infrastructure help us avoid breaks |
|
I think this just means you need to set up branch protection on the release/2.5.0-palantir.8 branch, or put bulldozer back into opt-in mode. |
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.
Releasing 2.5.0-palantir.8 from this branch as 3.0.0-palantir.26
@rahij @vinooganesh @gatesn