Skip to content

Conversation

A-CGray
Copy link
Member

@A-CGray A-CGray commented May 14, 2025

Purpose

Forgot to do this in #44

Expected time until merged

Type of change

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (non-backwards-compatible fix or feature)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Documentation update
  • Maintenance update
  • Other (please describe)

Testing

Checklist

  • I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
  • I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
  • I have run unit and regression tests which pass locally with my changes
  • I have added new tests that prove my fix is effective or that my feature works
  • I have added necessary documentation

@A-CGray A-CGray requested a review from a team as a code owner May 14, 2025 14:34
@A-CGray A-CGray requested a review from eirikurj May 14, 2025 14:34
@eirikurj eirikurj merged commit b4b60b5 into main May 15, 2025
17 checks passed
@marcomangano marcomangano deleted the A-CGray-patch-1 branch May 15, 2025 15:23
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