-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name refactoring for tests, growth, and median #503
Conversation
Co-authored-by: Matthew-Supernaw-NOAA <matthew.supernaw@noaa.gov> Co-authored-by: Nathan Vaughan <nathanvaughan-NOAA@users.noreply.github.com> Co-authored-by: Kelli Johnson <kelli.johnson@noaa.gov> Do not change median_Ro
Co-authored-by: Matthew-Supernaw-NOAA <matthew.supernaw@noaa.gov> Co-authored-by: Nathan Vaughan <nathanvaughan-NOAA@users.noreply.github.com> Co-authored-by: Kelli Johnson <kelli.johnson@noaa.gov>
We know we are a couple of commits behind main but given the large number of open pull requests we were leaving another rebase until this is ready to be merged into main. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Thanks for the name refactoring. I can help with merging these changes into the main branch once the conflicts are resolved.
Codecov ReportAttention:
... and 8 files with indirect coverage changes 📢 Thoughts on this report? Let us know!. |
@ChristineStawitz-NOAA Looks like we already found a scenario where the merge block is an issue. This pull request says it cannot be rebased due to conflicts and it will now only let me choose Squash and merge which I don't want to do because these are 4 different issues that would be best kept separate for future interpretability. |
@nathanvaughan-NOAA I came to the same conclusion once I tried to approve :) I removed that setting |
Hahaha sounds good, I'll merge once I fix these merge conflicts :) |
What is the feature?
How have you implemented the solution?
We have refactored the code base to change names as described.
Does the PR impact any other area of the project?
No this should not impact the rest of the code
How to test this change
Developer pre-PR checklist