Skip to content
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

feature 497 headers #336

Merged
merged 2 commits into from
Nov 10, 2023
Merged

feature 497 headers #336

merged 2 commits into from
Nov 10, 2023

Conversation

lisagoodrich
Copy link
Contributor

@lisagoodrich lisagoodrich commented Nov 10, 2023

Pull Request Testing

  • Describe testing already performed for these changes:
    . This issue had to be re-opened due to confusion about the best way to label index.rst files. They are treated differently depending on where they are located. Below are notes from @jprestop.

dtcenter/METviewer#502 (comment)
@lisagoodrich Thanks for all of your work on this task. I added a few suggestions that you can just accept the changes for, however, for the top level docs/index.rst, could you please change those headers back to what they were? Let me know if you want to talk about this again, but we had discussed how the top level index wasn't really a "part" whereas the User's Guide's and Contributor's Guide's index.rst files were "parts". So, we decided just to leave the top level index.rst files alone. You can verify this by looking at the already merged METplotpy file (https://raw.githubusercontent.com/dtcenter/METplotpy/develop/docs/index.rst) and the already merged METplus file (https://raw.githubusercontent.com/dtcenter/METplus/develop/docs/index.rst). METcalcpy was also completed but it looks like it is not the same as the others and needs to be fixed as well (https://raw.githubusercontent.com/dtcenter/METcalcpy/develop/docs/index.rst) - apologies for missing that in PR review of METcalcpy.

  • Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
    Confirm the header change is correct, using = instead of #.
    Please squash and merge and close the branch. I don't have permission to do this.

  • Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No errors]

  • [ x Do these changes include sufficient testing updates? [Yes]

  • Will this PR result in changes to the test suite? [No]

    If yes, describe the new output and/or changes to the existing output:

  • Please complete this pull request review by [11/13/23].

Pull Request Checklist

See the METplus Workflow for details.

  • Add any new Python packages to the METplus Components Python Requirements table.
  • Review the source issue metadata (required labels, projects, and milestone).
  • Complete the PR definition above.
  • Ensure the PR title matches the feature or bugfix branch name.
  • Define the PR metadata, as permissions allow.
    Select: Reviewer(s)
    Select: Organization level software support Project or Repository level development cycle Project
    Select: Milestone as the version that will include these changes
  • After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
  • After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
  • Close the linked issue and delete your feature or bugfix branch from GitHub.

@lisagoodrich lisagoodrich added this to the METcalcpy-2.1.1 (bugfix) milestone Nov 10, 2023
@lisagoodrich lisagoodrich linked an issue Nov 10, 2023 that may be closed by this pull request
7 tasks
@jprestop
Copy link
Collaborator

@lisagoodrich I changed the Project from METplus-Wrappers-6.0.0 Development to METplus-Analysis-6.0.0 Development since this PR is for METcalcpy and not for METplus wrappers. I also changed the Milestone from METcalcpy-2.1.1 Bugfix to METcalcpy-3.0.0 since this isn't a bugfix but rather a change for the upcoming release.

@jprestop jprestop changed the title changing header for continuity feature 497 headers Nov 10, 2023
Copy link
Collaborator

@jprestop jprestop left a comment

Choose a reason for hiding this comment

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

Thanks @lisagoodrich for your work on this task. I have verified that all tests pass. I approve this request.

@lisagoodrich
Copy link
Contributor Author

@jprestop who do I ask to Merge this pull request? I'm unable to merge it. Thank you for making corrections to the projects and developments.

@jprestop
Copy link
Collaborator

HI @lisagoodrich. I'm sorry, I always forget that you do not have squash and merge permissions here. :( I will take care of it.

@jprestop jprestop merged commit fcf7c3f into develop Nov 10, 2023
6 checks passed
@jprestop jprestop deleted the feature_497_headers branch November 10, 2023 21:44
jprestop added a commit that referenced this pull request Feb 2, 2024
* Prepare for next release

* add missing end quote to fix package install

* reset_index is performed on the float value #322 (#323)

* Update release notes (#328)

* Update release-notes.rst formatting

* Update and rename 2.1.0_wcoss2 to 3.0.0_wcoss2

* loop over statistics only once to avoid data multiplication #330 (#331)

* Added sphinx_rtd_theme to extensions

* Updated requirements.txt

* Added pillow

* feature 497 headers (#336)

* changing header for continuity

* Modified the other headers in the file to be consistent with other repos

---------

Co-authored-by: Julie Prestopnik <jpresto@ucar.edu>

* Beta2 release (#338)

* Next version

* Feature 332 di doc (#333)

* Add difficulty index documentation

* Add more documentation

* Add more definition

* Fix indent

* Add figure

* fix indentation

* fix equations

* Add table

* Added remaining tables

* fix table issue

* Add links

* formatting

* change link to latest

---------

Co-authored-by: Tracy <tracy.hertneky@noaa.gov>

* Additions to beta2 release (#340)

* Next beta

* Bugfix 329 negative bcmse (#344)

* Issue #329 return 0 if negative BCMSE value is calculated

* Issue #329 add test for calculate_bcmse() in the sl1l2_statistics module

* Issue #392 added test_sl1l2.py to the list of pytests to run

* command line updates

* updating yaml file

---------

Co-authored-by: Hank Fisher <fisherh@ucar.edu>
Co-authored-by: George McCabe <23407799+georgemccabe@users.noreply.github.com>
Co-authored-by: John Halley Gotway <johnhg@ucar.edu>
Co-authored-by: Tatiana Burek <tatiana@ucar.edu>
Co-authored-by: jprestop <jpresto@ucar.edu>
Co-authored-by: Tracy Hertneky <39317287+hertneky@users.noreply.github.com>
Co-authored-by: Tracy <tracy.hertneky@noaa.gov>
Co-authored-by: bikegeek <3753118+bikegeek@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔎 In review
Development

Successfully merging this pull request may close these issues.

Documentation: Make Headers Consistent in METcalcpy User's Guides
2 participants