Skip to content

Conversation

@xjules
Copy link
Contributor

@xjules xjules commented Jan 20, 2026

Issue
Resolves #12655

Approach
Very WIP

(Screenshot of new behavior in GUI if applicable)

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure unit tests pass locally after every commit (git rebase -i main --exec 'just rapid-tests')

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Add backport label to latest release (format: 'backport release-branch-name')

@xjules xjules self-assigned this Jan 20, 2026
@xjules xjules added improvement Something nice to have, that will make life easier for developers or users or both. release-notes:user-impact Automatically categorise as breaking for people using CLI/GUI labels Jan 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Something nice to have, that will make life easier for developers or users or both. release-notes:user-impact Automatically categorise as breaking for people using CLI/GUI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Link DistanceESMDA to ESMDA workflow

1 participant