Skip to content

Simplify pull request checklist#7096

Open
trexfeathers wants to merge 6 commits into
SciTools:mainfrom
trexfeathers:contributing
Open

Simplify pull request checklist#7096
trexfeathers wants to merge 6 commits into
SciTools:mainfrom
trexfeathers:contributing

Conversation

@trexfeathers
Copy link
Copy Markdown
Contributor

@trexfeathers trexfeathers commented May 22, 2026

Description

  • Simplifies the pull request checklist
  • Moves the pull request checklist directly into the pull request template (see below) - to make it more immediate and therefore easier to follow
  • Updates several related pages with more detailed guidance on contributing

Checklist

(In addition to a full set of passing checks ✅)


Tip

Add any of the below labels to trigger actions on this PR:

  • benchmark_this Request that this pull request be benchmarked to check if it introduces performance shifts

Copy link
Copy Markdown
Contributor

@scitools-ci scitools-ci Bot left a comment

Choose a reason for hiding this comment

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

Templating

This PR includes changes that may be worth sharing via templating. For each file listed below, please either:

  • Action the suggestion via a pull request editing/adding the relevant file in the SciTools/.github templates/ directory. 1
  • Raise an issue against the SciTools/.github repo for the above action if you really don't have 10mins spare right now. Include an assignee, to avoid it being forgotten.
  • Dismiss the suggestion if the changes are not suitable for templating.

You will need to dismiss this review before this PR can be merged. Recommend the reviewer does this as their final action before merging, as this text will continually update as commits come in.

Templated files

The following changed files are templated:

Footnotes

  1. Include this text in the PR body to avoid any notifications about applying the template changes back to the source repo!
    @scitools-templating: please no update notification on: iris

@codecov
Copy link
Copy Markdown

codecov Bot commented May 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.13%. Comparing base (3d16556) to head (8a74da3).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7096   +/-   ##
=======================================
  Coverage   90.13%   90.13%           
=======================================
  Files          91       91           
  Lines       24957    24957           
  Branches     4684     4684           
=======================================
  Hits        22496    22496           
  Misses       1683     1683           
  Partials      778      778           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This was VERY wordy for something expected of all contributors. I didn't feel comfortable linking to it in the PR checklist. So I have separated it into a TLDR essentials, and retained the previous notes in a separate Details section.

Comment on lines -22 to -23
#. **Include a "What's New" entry**, if appropriate.
See :ref:`whats_new_contributions`.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Migrated to the PR template

Comment on lines -32 to -34
#. **Check all new dependencies added to the** `requirements`_ **yaml
files.** If dependencies have been added then new nox testing lockfiles
should be generated too, see :ref:`gha_test_env`.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Migrated to the PR template

Comment on lines -36 to -38
#. **Check the source documentation been updated to explain all new or changed
features**. Note, we now use numpydoc strings. Any touched code should
be updated to use the docstrings formatting. See :ref:`docstrings`.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Migrated to the PR template

Comment on lines -40 to -41
#. **Include code examples inside the docstrings where appropriate**. See
:ref:`contributing.documentation.testing`.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Migrated to the PR template

Comment on lines -43 to -44
#. **Check the documentation builds without warnings or errors**. See
:ref:`contributing.documentation.building`
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

NOT migrated to the PR template - this is implicitly addressed by the CI checks.

Comment on lines -46 to -48
#. **Check for any new dependencies in the** `readthedocs.yml`_ **file**. This
file is used to build the documentation that is served from
https://scitools-iris.readthedocs.io/en/latest/
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

NOT migrated to the PR template - this is too specific to be worth calling out. The RTD build is part of the CI checks (that might not have been true when this was written), so will flag any [rare] dependency failures before the PR is merged.

Comment on lines -50 to -61
#. **Check for updates needed for supporting projects for test or example
data**. For example:

* `iris-test-data`_ is a github project containing all the data to support
the tests.
* `iris-sample-data`_ is a github project containing all the data to support
the gallery and examples.

If new files are required by tests or code examples, they must be added to
the appropriate supporting project via a suitable pull-request. This pull
request should be referenced in the main Iris pull request and must be
accepted and merged before the Iris one can be.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

NOT migrated to the PR template - this is too specific to be worth calling out. I moved the text into contributing_ci_tests.rst, and that is linked from the template, so hopefully that's enough breadcrumbs for the rare times when this point is important.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This was written when we first introduced pre-commit, specifically to handle the black linting tool. The use has now grown, and evolves rapidly, so I made two types of change:

  • Removed any out-dated information
  • Rephrased to make this page less vulnerable to going out of date again

Comment thread benchmarks/README.md
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No 'content' changed here, only formatting:

  • Take advantage of GitHub Markdown 'alerts'
  • Take advantage of GitHub Markdown footnotes
  • Format the Environment Variables section into a table structure

@trexfeathers
Copy link
Copy Markdown
Contributor Author

...
This PR includes changes that may be worth sharing via templating. For each file listed below, please either:
...

See SciTools/.github#264

@ESadek-MO ESadek-MO self-assigned this May 22, 2026
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@ESadek-MO we might consider some messaging in here to avoid scaring new contributors? Some form of "we can help, don't worry".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants