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

Update dependency pretty-quick to v1.5.0 #132

Merged
merged 1 commit into from May 18, 2018
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 18, 2018

This Pull Request updates dependency pretty-quick from v1.4.1 to v1.5.0

Note: This PR was created on a configured schedule ("on the first day of the month") and will not receive updates outside those times.

Release Notes

v1.5.0

Compare Source

Features
  • safer handling of partially staged files (#​29) (cc69fb3)


This PR has been generated by Renovate Bot.

@react-tether-bot
Copy link

Messages
📖

Hey @renovate[bot], thanks for submitting a pull request! 😸

📖

🤔 Hmmm, code coverage is looking low for the whole codebase.

Coverage in All Files

File Line Coverage Statement Coverage Function Coverage Branch Coverage
src/react-tether.js (0/0) 100% (0/0) 100% (0/0) 100% (0/0) 100%
src/TetherComponent.jsx (67/80) 84% (67/80) 84% (17/24) 71% (35/46) 76%
Total (67/80) 84% (67/80) 84% (17/24) 71% (35/46) 76%

Generated by 🚫 dangerJS

@coveralls
Copy link

Pull Request Test Coverage Report for Build 224

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 80.952%

Totals Coverage Status
Change from base Build 221: 0.0%
Covered Lines: 67
Relevant Lines: 80

💛 - Coveralls

@renovate renovate bot merged commit 70dd543 into master May 18, 2018
@renovate renovate bot deleted the renovate/pretty-quick-1.x branch May 18, 2018 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants