Skip to content

skpkg: doc migration #342

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

Merged
merged 3 commits into from
Jun 11, 2025
Merged

Conversation

cadenmyers13
Copy link
Contributor

When I built docs locally, I got a lot of warning messages referring to docstring formatting and other doc formatting. However, these warnings persists on the current version of diffpy.utils leading me to believe that there are some formatting issues with the current rst files where the docs exists (which i left unchanged).

Copy link

codecov bot commented Jun 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (21c9220) to head (b14be77).
Report is 5 commits behind head on migration.

Additional details and impacted files
@@             Coverage Diff             @@
##           migration      #342   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
===========================================
  Files              9         9           
  Lines            516       516           
===========================================
  Hits             516       516           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sbillinge sbillinge merged commit 6d739fd into diffpy:migration Jun 11, 2025
4 checks passed
@sbillinge
Copy link
Contributor

thanks @cadenmyers13 I saw your note. We can look into those formatting warnings on another PR. For now, this is nicely done to bring things up to skpkg 0.1.0 standards which is the current task at hand so I merged. I appreciate you creating the issue for that other work.

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.

2 participants