forked from scoverage/sbt-scoverage
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rebase to parent #6
Open
pzhong-livongo
wants to merge
90
commits into
integration
Choose a base branch
from
beplat-72-rebase
base: integration
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
…teInReadme Fixed README to say you do not need to run coverageReport before coverageAggregate
…rsion-full Build CrossVersion.full
We no longer cross publishing for sbt, and therefore don't need to do the cross test
Remove cross from release
Running that extra matrix doesn't add anything to CI. I plan on fully redoing the CI, but want to get this just released first
Bump pgp plugin and remove extra matrix.
Fix shields
Correct report location in readme.
Update CI and release strategy
Remove no longer needed travis file
Also add in buildInfo to re-use version in build
Update to scoverage 1.4.4.
I don't want to have to update the readme every release...
Remove explicit version in example in docs.
Add in missing percent sign for branch coverage
Reformatting an entire project typically has the complaint that blame is no longer useful. Thankfully, git has a solution for this. You can read more about this here: https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame This `.git-blame-ignore-revs` file can be used to ensure that the formatting commit is ignored when locally using `git blame.`
Add in .git-blame-ignore-revs
Bump scoverage version to 1.4.7
…verage-plugin-1.4.8 Update scalac-scoverage-plugin to 1.4.8
Update sbt, scripted-plugin to 1.5.3
Update to scala 2.12.14
Update sbt, scripted-plugin to 1.5.4
…mt-2.4.3 Update sbt-scalafmt to 2.4.3
Update sbt, scripted-plugin to 1.5.5
…ore-3.0.0 Update scalafmt-core to 3.0.0
…ore-3.0.1 Update scalafmt-core to 3.0.1
…ore-3.0.2 Update scalafmt-core to 3.0.2
Rebase to Main branch of parent project
Co-authored-by: Chris Kipp <[email protected]>
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.
No description provided.