-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish / publish setup tweaks #1432
Publish / publish setup tweaks #1432
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
adbcab8
to
88cb65a
Compare
4ff058a
to
2d8399b
Compare
2d8399b
to
7132b93
Compare
7132b93
to
a177379
Compare
a177379
to
b1b5c03
Compare
7ac7bed
to
9f15e05
Compare
About this PR: I've been wanting to write non regression tests for it, but I don't recall exactly which scenarios it's fixing. But from what I recall, it's definitely useful, and the publish command should have been written this way initially IMO. And as it doesn't break any existing test, my opinion is that it can be merged as is… |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Things I tweaked / fixed for the demo of my Scalacon talk.