-
Notifications
You must be signed in to change notification settings - Fork 56
Resolve #161. #162
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
Resolve #161. #162
Conversation
#153) * Replace travis-ci config with GitHub action to create a CI build including codecov report and upload. * Replace Travis-CI badge with GitHub action badge * Fix GitHub action badge * Replace equal sign paragraph in readme with something more dynamic.
Bumps commons-io from 2.10.0 to 2.11.0. --- updated-dependencies: - dependency-name: commons-io:commons-io dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [failsafe](https://github.com/jhalterman/failsafe) from 2.4.0 to 2.4.1. - [Release notes](https://github.com/jhalterman/failsafe/releases) - [Changelog](https://github.com/jhalterman/failsafe/blob/master/CHANGES.md) - [Commits](failsafe-lib/failsafe@failsafe-2.4.0...failsafe-2.4.1) --- updated-dependencies: - dependency-name: net.jodah:failsafe dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…lsafe-2.4.1 Bump failsafe from 2.4.0 to 2.4.1
Bumps [failsafe](https://github.com/failsafe-lib/failsafe) from 2.4.1 to 2.4.2. - [Release notes](https://github.com/failsafe-lib/failsafe/releases) - [Changelog](https://github.com/failsafe-lib/failsafe/blob/master/CHANGELOG.md) - [Commits](failsafe-lib/failsafe@failsafe-2.4.1...failsafe-2.4.2) --- updated-dependencies: - dependency-name: net.jodah:failsafe dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…lsafe-2.4.2 Bump failsafe from 2.4.1 to 2.4.2
Bumps [maven-scm-plugin](https://github.com/apache/maven-scm) from 1.11.2 to 1.11.3. - [Release notes](https://github.com/apache/maven-scm/releases) - [Commits](apache/maven-scm@maven-scm-1.11.2...maven-scm-1.11.3) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-scm-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps maven-scm-provider-gitexe from 1.11.2 to 1.11.3. --- updated-dependencies: - dependency-name: org.apache.maven.scm:maven-scm-provider-gitexe dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…ven.plugins-maven-scm-plugin-1.11.3 Bump maven-scm-plugin from 1.11.2 to 1.11.3
…ven.scm-maven-scm-provider-gitexe-1.11.3 Bump maven-scm-provider-gitexe from 1.11.2 to 1.11.3
Currently CodeQL runs for every PR which causes issues because CodeQL works by comparing to prior runs which there are no if it is a brand-new branch,
Backmerge master to PR
Codecov Report
@@ Coverage Diff @@
## 1.1.0_dev #162 +/- ##
============================================
Coverage 57.97% 57.97%
Complexity 127 127
============================================
Files 8 8
Lines 621 621
Branches 41 41
============================================
Hits 360 360
Misses 232 232
Partials 29 29
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Fix syntax error
diemol
left a comment
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.
Thank you, @sceiler!
Update codeql-analysis.yml
Description
This resolves #161.
Motivation and Context
This resolves #161.
How Has This Been Tested?
Unit tests and E2E test.
Types of changes
Screenshots (if appropriate):
Checklist
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...