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

Resolved Sphinx warnings #427

Merged
merged 1 commit into from
Oct 11, 2023
Merged

Resolved Sphinx warnings #427

merged 1 commit into from
Oct 11, 2023

Conversation

mjcaley
Copy link
Owner

@mjcaley mjcaley commented Oct 11, 2023

No description provided.

@codecov
Copy link

codecov bot commented Oct 11, 2023

Codecov Report

Merging #427 (508b05f) into development (3634e1d) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           development      #427   +/-   ##
=============================================
  Coverage       100.00%   100.00%           
=============================================
  Files               11        11           
  Lines             1194      1194           
  Branches           147       147           
=============================================
  Hits              1194      1194           
Flag Coverage Δ
integrationtests 63.14% <ø> (ø)
unittests 100.00% <ø> (ø)

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

Files Coverage Δ
aiospamc/cli.py 100.00% <ø> (ø)
aiospamc/connections.py 100.00% <ø> (ø)
aiospamc/frontend.py 100.00% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@mjcaley mjcaley merged commit ee8fd62 into development Oct 11, 2023
26 checks passed
@mjcaley mjcaley deleted the fix-sphinx-warnings branch October 11, 2023 01:54
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

1 participant