Skip to content

Conversation

@zachdaniel
Copy link
Owner

@zachdaniel zachdaniel commented Mar 18, 2020

Contributor checklist

  • My commit messages follow the Conventional Commit Message Format
    For example: fix: Multiply by appropriate coefficient, or
    feat(Calculator): Correctly preserve history
    Any explanation or long form information in your commit message should be
    in a separate paragraph, separated by a blank line from the primary message
  • Bug fixes include regression tests
  • Features include unit/acceptance tests

@coveralls
Copy link

coveralls commented Mar 18, 2020

Pull Request Test Coverage Report for Build 124

  • 11 of 12 (91.67%) changed or added relevant lines in 2 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage increased (+0.2%) to 85.714%

Changes Missing Coverage Covered Lines Changed/Added Lines %
lib/mix/tasks/git_ops.release.ex 3 4 75.0%
Files with Coverage Reduction New Missed Lines %
lib/mix/tasks/git_ops.release.ex 1 75.38%
Totals Coverage Status
Change from base Build 120: 0.2%
Covered Lines: 240
Relevant Lines: 280

💛 - Coveralls

@zachdaniel zachdaniel force-pushed the parse-multiple-messages branch from 57cb1a8 to ed04ef4 Compare March 25, 2020 17:58
@sourcelevel-bot
Copy link

SourceLevel has finished reviewing this Pull Request and has found:

  • 1 fixed issue! 🎉

See more details about this review.

@zachdaniel zachdaniel merged commit 32dcc16 into master Mar 25, 2020
@zachdaniel zachdaniel deleted the parse-multiple-messages branch March 25, 2020 18:01
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.

3 participants