Skip to content

[chore] force Github CI Action to use default maven build profile #441

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

Merged
merged 1 commit into from
Oct 17, 2019

Conversation

dariuszkuc
Copy link
Collaborator

No description provided.

@dariuszkuc
Copy link
Collaborator Author

Unsure why Github Actions ignore the activeByDefault setting.

@codecov-io
Copy link

codecov-io commented Oct 17, 2019

Codecov Report

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

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #441   +/-   ##
=========================================
  Coverage     97.75%   97.75%           
  Complexity      327      327           
=========================================
  Files           106      106           
  Lines          1248     1248           
  Branches        207      207           
=========================================
  Hits           1220     1220           
  Misses            7        7           
  Partials         21       21

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 234fe0e...0f987c5. Read the comment docs.

@smyrick smyrick added the type: tool update CI, code coverage, or linter updates label Oct 17, 2019
@smyrick smyrick merged commit 816cbd5 into ExpediaGroup:master Oct 17, 2019
@dariuszkuc dariuszkuc deleted the ci branch October 17, 2019 20:48
dariuszkuc added a commit to dariuszkuc/graphql-kotlin that referenced this pull request Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: tool update CI, code coverage, or linter updates
Development

Successfully merging this pull request may close these issues.

3 participants