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

fix: incorrectly calculates next semantic version with large commit bodies containing possible keywords #371

Merged
merged 1 commit into from
Aug 25, 2023

Conversation

ga-paul-t
Copy link
Collaborator

closes #359

@codecov-commenter
Copy link

Codecov Report

Merging #371 (d51a1ff) into main (309fd5c) will decrease coverage by 0.28%.
The diff coverage is 73.91%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##             main     #371      +/-   ##
==========================================
- Coverage   80.69%   80.42%   -0.28%     
==========================================
  Files          40       40              
  Lines        1865     1900      +35     
==========================================
+ Hits         1505     1528      +23     
- Misses        268      277       +9     
- Partials       92       95       +3     
Files Changed Coverage Δ
internal/semver/parser.go 73.91% <73.33%> (-26.09%) ⬇️
internal/task/nextsemver/nextsemver.go 88.34% <100.00%> (ø)

@ga-paul-t ga-paul-t merged commit af8eb91 into main Aug 25, 2023
@ga-paul-t ga-paul-t deleted the fix-incorrect-increment branch August 25, 2023 05:21
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.

[Bug]: incorrectly calculates next semantic version with large commit bodies containing possible keywords
2 participants