Skip to content

Fix: Build composer-normalize.phar in Continuous Integration workflow #293

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
Dec 25, 2019

Conversation

localheinz
Copy link
Member

This PR

  • compiles composer-normalize.phar in the Continuous Integration workflow

Follows #292.

💁‍♂ This way we'll now when we broke something before tagging a release.

Sorry, something went wrong.

Verified

This commit was signed with the committer’s verified signature.
localheinz Andreas Möller
@localheinz localheinz added the bug label Dec 25, 2019
@localheinz localheinz self-assigned this Dec 25, 2019
@codecov
Copy link

codecov bot commented Dec 25, 2019

Codecov Report

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

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #293   +/-   ##
=========================================
  Coverage     84.94%   84.94%           
  Complexity       37       37           
=========================================
  Files             3        3           
  Lines           186      186           
=========================================
  Hits            158      158           
  Misses           28       28

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 b89248f...3013cb7. Read the comment docs.

@localheinz localheinz merged commit 198e4bd into master Dec 25, 2019
@localheinz localheinz deleted the fix/build branch December 25, 2019 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant