Move assertj code -> palantir/assertj-automation #1125
Merged
Conversation
This file contains 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
Generate changelog in
|
iamdanfox
changed the title
iamdanfox
requested review from
carterkozak
and removed request for
dansanduleac
|
👍 |
|
🚂 |
|
Released 2.44.0 |
This was referenced Dec 17, 2019
This was referenced Dec 17, 2019
This was referenced Jan 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before this PR
Internally, many excavators to update people's baseline would not auto-merge because they make some trivial assertj changes (which require a human +1).
After this PR
==COMMIT_MSG==
All assertj-related code-rewriting now lives in the https://github.com/palantir/assertj-automation repo.
==COMMIT_MSG==
Possible downsides?
com.palantir.assertj-automation:assertj-error-prone