skpkg: misc config and other file changes

[cadenmyers13]

Final PR for the current skpkg'ing of diffpy.utils! After this is merged we should be able to merge migration into main once tested.

I had to install sphinx-copybutton to build docs locally so i added that to requirements. Maybe this needs to be added to scikit-package?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b14be77) to head (9f3e153).
Report is 8 commits behind head on migration.

Additional details and impacted files

@@             Coverage Diff             @@
##           migration      #344   +/-   ##
===========================================
  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]

I had to install sphinx-copybutton to build docs locally so i added that to requirements. Maybe this needs to be added to scikit-package?

I believe it is already in scikit-package v0.1.0. It is just you built your env using requirements/docs.txt before updating.....

[cadenmyers13]

@sbillinge Oh you're right, I must've got rid of it when I moved requirements over!

[sbillinge]

looks good. I am confused now, because I believe that copybutton is in skpkg 0.1.0 so I am not sure why you are having to manually add it here. Please see my other comment and then I an merge.

[cadenmyers13]

@sbillinge see above response about copybutton, it was a fault on my end!

[sbillinge]

@sbillinge Oh you're right, I must've got rid of it when I moved requirements over!

slow and steady wins the race!

[sbillinge]

Brilliant, is that a wrap (bar testing)?

[cadenmyers13]

@sbillinge yep!

[cadenmyers13]

@sbillinge pytest passes on a fully sync'd migration branch. Is there any other testing that needs to be done?

[sbillinge]

normally we would quickly run through any tutorial. Could you take a look if there is one? But then we can merge. I htink you can create a PR, migration -> main when you are ready.

[sbillinge]

@cadenmyers13 don't forget the "closes #" close the skpkg issue for that migration -> main PR.

[cadenmyers13]

@cadenmyers13 don't forget the "closes #" close the skpkg issue for that migration -> main PR.

@sbillinge will do. There are tutorials for this. ill run them and let you know if i run into any bugs