Skip to content
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

Pass sbt settings without varargs expansion #1826

Merged
merged 1 commit into from
Aug 28, 2017

Conversation

fthomas
Copy link
Member

@fthomas fthomas commented Aug 18, 2017

This is a cosmetic change that has been possible since sbt 0.13.8:
https://github.com/sbt/sbt/releases/tag/v0.13.8

This is a cosmetic change that has been possible since sbt 0.13.8:
https://github.com/sbt/sbt/releases/tag/v0.13.8
@codecov-io
Copy link

codecov-io commented Aug 18, 2017

Codecov Report

Merging #1826 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1826   +/-   ##
=======================================
  Coverage   94.96%   94.96%           
=======================================
  Files         241      241           
  Lines        4173     4173           
  Branches      106      106           
=======================================
  Hits         3963     3963           
  Misses        210      210

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 68a8666...6ab074b. Read the comment docs.

@kailuowang kailuowang merged commit d336d45 into typelevel:master Aug 28, 2017
@fthomas fthomas deleted the topic/sbt-varargs branch August 28, 2017 20:01
LukaJCB pushed a commit to LukaJCB/cats that referenced this pull request Sep 1, 2017
@kailuowang kailuowang added this to the 1.0.0-RC1 milestone Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants