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

make stage more explicit #2828

Merged
merged 2 commits into from
Jul 8, 2019
Merged

make stage more explicit #2828

merged 2 commits into from
Jul 8, 2019

Conversation

kailuowang
Copy link
Contributor

@kailuowang kailuowang commented May 3, 2019

This also results in a very short lint stage and a longer test stage, which was my original intention.

@codecov-io
Copy link

codecov-io commented May 4, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2828   +/-   ##
=======================================
  Coverage   94.03%   94.03%           
=======================================
  Files         370      370           
  Lines        7038     7038           
  Branches      186      186           
=======================================
  Hits         6618     6618           
  Misses        420      420

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 6d29f7b...794b3c2. Read the comment docs.

@rossabaker
Copy link
Member

What runs scalastyle now?

@kailuowang
Copy link
Contributor Author

@rossabaker, my bad. Forgot to mention that I removed it since scalafmt is much more strict, scalastyle keeps failing on parsing from time to time. Not sure if we need to maintain two sets of styling rules.

@rossabaker
Copy link
Member

In that case, validateJVM still calls it. If we're not going to enforce it on the build, we should also remove it from there. It's also still mentioned in CONTRIBUTING.md.

We could even go a step further and remove the config and the plugin, unless we think it's still providing some marginal value when run manually.

@kailuowang
Copy link
Contributor Author

@rossabaker good point. I will udpate this PR with complete scalastyle removal.

@kailuowang
Copy link
Contributor Author

kailuowang commented Jul 8, 2019

@rossabaker scalastyle was removed in another PR and merged. This one is good to go right?

Copy link
Member

@rossabaker rossabaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@kailuowang kailuowang merged commit baf0b48 into master Jul 8, 2019
@rossabaker rossabaker deleted the kailuowang-patch-7 branch July 8, 2019 16:21
@kailuowang kailuowang added this to the 2.0.0-RC1 milestone Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants