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

hotfix: bad default_time value type introduced in #300 #302

Merged
merged 1 commit into from
Jun 23, 2024

Conversation

Guts
Copy link
Owner

@Guts Guts commented Jun 23, 2024

No description provided.

@github-actions github-actions bot added the bug Something isn't working label Jun 23, 2024
Copy link

sonarcloud bot commented Jun 23, 2024

Copy link

codecov bot commented Jun 23, 2024

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 80.48%. Comparing base (9b88745) to head (15bb7b5).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #302      +/-   ##
==========================================
+ Coverage   80.45%   80.48%   +0.03%     
==========================================
  Files           9        9              
  Lines         614      615       +1     
  Branches      128      128              
==========================================
+ Hits          494      495       +1     
  Misses         83       83              
  Partials       37       37              
Flag Coverage Δ
unittests 80.48% <50.00%> (+0.03%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
mkdocs_rss_plugin/plugin.py 90.00% <50.00%> (+0.07%) ⬆️

@Guts Guts merged commit 980c498 into main Jun 23, 2024
9 checks passed
@Guts Guts deleted the fix/bad-default_time-type-introduced-in-300 branch June 23, 2024 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant