Skip to content

Conversation

w-k-jones
Copy link
Member

@w-k-jones w-k-jones commented Jul 17, 2025

  • Have you followed our guidelines in CONTRIBUTING.md?
  • Have you self-reviewed your code and corrected any misspellings?
  • Have you written documentation that is easy to understand?
  • Have you written descriptive commit messages?
  • Have you added NumPy docstrings for newly added functions?
  • Have you formatted your code using black?
  • If you have introduced a new functionality, have you added adequate unit tests?
  • Have all tests passed in your local clone?
  • If you have introduced a new functionality, have you added an example notebook?
  • Have you kept your pull request small and limited so that it is easy to review?
  • Have the newest changes from this branch been merged?

@w-k-jones w-k-jones self-assigned this Jul 17, 2025
@w-k-jones w-k-jones added the release Organising the next release on conda-forge label Jul 17, 2025
@w-k-jones w-k-jones mentioned this pull request Jul 17, 2025
9 tasks
Copy link

codecov bot commented Jul 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.55%. Comparing base (aae14ed) to head (03fe328).
Report is 4 commits behind head on RC_v1.6.x.

Additional details and impacted files
@@            Coverage Diff             @@
##           RC_v1.6.x     #518   +/-   ##
==========================================
  Coverage      63.55%   63.55%           
==========================================
  Files             27       27           
  Lines           3844     3844           
==========================================
  Hits            2443     2443           
  Misses          1401     1401           
Flag Coverage Δ
unittests 63.55% <100.00%> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link

Linting results by Pylint:

Your code has been rated at 8.31/10 (previous run: 8.31/10, +0.00)
The linting score is an indicator that reflects how well your code version follows Pylint’s coding standards and quality metrics with respect to the RC_v1.6.x branch.
A decrease usually indicates your new code does not fully meet style guidelines or has potential errors.

Copy link
Member

@freemansw1 freemansw1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for managing this @w-k-jones

@w-k-jones w-k-jones merged commit afd4851 into tobac-project:RC_v1.6.x Jul 17, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Organising the next release on conda-forge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants