You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ If you're running the coverage reports from within an sbt console session (as
42
42
opposed to one command per sbt launch), then the `coverage` command is sticky. To
43
43
turn it back off when you're done running reports, use the `coverageOff` command or reset `coverageEnabled` with `set coverageEnabled := false`.
44
44
45
-
Sample project with scoverage in both sbt and maven - [the scoverage samples project](https://github.com/scoverage/scoverage-samples).
45
+
Sample project with scoverage in both sbt and maven - [the scoverage samples project](https://github.com/scoverage/sbt-scoverage-samples).
46
46
47
47
## Notes on upgrading to version 1.3.0
48
48
@@ -116,7 +116,7 @@ If you are running into a scenario where your tests normally pass, but fail when
116
116
117
117
## Coveralls
118
118
119
-
If you have an open source project then you can add code coverage metrics with the excellent website http://coveralls.io. Scoverage will integrate with coveralls using the [sbt-coveralls](https://github.com/scoverage/sbt-coveralls) plugin.
119
+
If you have an open source project then you can add code coverage metrics with the excellent website https://coveralls.io/ Scoverage will integrate with coveralls using the [sbt-coveralls](https://github.com/scoverage/sbt-coveralls) plugin.
0 commit comments