Skip to content

Conversation

hwikle-lanl
Copy link
Collaborator

Code review checklist:

  • Code is generally sensical and well commented
  • Variable/function names all telegraph their purpose and contents
  • Functions/classes have useful doc strings
  • Function arguments are typed
  • Added/modified unit tests to cover changes.
  • New features have documentation added to the docs.
  • New features and backwards compatibility breaks are noted in the RELEASE.md

@hwikle-lanl hwikle-lanl added this to the 2.5 milestone May 20, 2025
@hwikle-lanl hwikle-lanl requested a review from Paul-Ferrell May 20, 2025 20:57
@hwikle-lanl hwikle-lanl self-assigned this May 20, 2025
@hwikle-lanl hwikle-lanl linked an issue May 20, 2025 that may be closed by this pull request
@hwikle-lanl hwikle-lanl force-pushed the 710-allowing-tagging-of-specific-results-values-as-important branch from f03d2b8 to 9cd2740 Compare May 20, 2025 20:58
@hwikle-lanl hwikle-lanl changed the title Alloq tagging of specific results values as important Allow tagging of specific results values as important May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allowing tagging of specific results values as important.
1 participant