Skip to content
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

Enhancement: Use ergebnis/composer-normalize instead of localheinz/composer-normalize #164

Merged
merged 1 commit into from Dec 17, 2019

Conversation

localheinz
Copy link
Member

This PR

  • uses ergebnis/composer-normalize instead of localheinz/composer-normalize

💁‍♂ For reference, see https://localheinz.com/blog/2019/12/10/from-localheinz-to-ergebnis/.

@localheinz localheinz self-assigned this Dec 17, 2019
@codecov
Copy link

codecov bot commented Dec 17, 2019

Codecov Report

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

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #164   +/-   ##
=========================================
  Coverage     90.63%   90.63%           
  Complexity      135      135           
=========================================
  Files            22       22           
  Lines           395      395           
=========================================
  Hits            358      358           
  Misses           37       37

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 e360dfe...60a99ee. Read the comment docs.

@localheinz localheinz merged commit 3e7e13b into master Dec 17, 2019
@localheinz localheinz deleted the feature/composer-normalize branch December 17, 2019 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant