Backmerge #168
Merged
Backmerge #168
Conversation
This file contains hidden or 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
#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,
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.
Description
Motivation and Context
How Has This Been Tested?
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...