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

Validate kinds match config in fragment when batching release notes #711

Conversation

miniscruff
Copy link
Owner

Closes #688

Check the following

  • Maintain high code coverage
  • Be properly formatted
  • Documentation changes are included
  • Include a change file if expected

Additional context
Really should have been in the last release

Copy link

codacy-production bot commented Sep 8, 2024

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for 49bf31d1 100.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (49bf31d) Report Missing Report Missing Report Missing
Head commit (8be2fad) 2466 2293 92.98%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#711) 2 2 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

Footnotes

  1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

@miniscruff miniscruff merged commit fcad6bc into main Sep 8, 2024
4 of 5 checks passed
@miniscruff miniscruff deleted the 688-invalid-kind-does-not-throw-an-error-without-a-kind-format-configured branch September 8, 2024 08:14
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.

Invalid kind does not throw an error without a kind format configured
1 participant