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

@trexfeathers trexfeathers commented May 22, 2026

Copy link
Copy Markdown
Contributor

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

@scitools-ci scitools-ci Bot left a comment

Copy link
Copy Markdown
Contributor

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

codecov Bot commented May 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.13%. Comparing base (3d16556) to head (8a74da3).
⚠️ Report is 10 commits behind head on main.

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 Harness.
📢 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.

Comment thread docs/src/developers_guide/documenting/whats_new_contributions.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_pull_request_checklist.rst
Comment thread docs/src/developers_guide/contributing_code_formatting.rst
Comment thread benchmarks/README.md
@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".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yeah, I'd agree, I think that'd be nice. I can't think of phrasing though 😂

@ESadek-MO ESadek-MO left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Honestly looks great, I can't see anything controversial, which is always unsettling on documentation 😂

A couple questions, and your original suggestion to add a lifeline to the checklist for newer users, and I think it'd be good to go.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yeah, I'd agree, I think that'd be nice. I can't think of phrasing though 😂

Git Conflicts
=============
It should describe your change in a few sentences, with particular focus on
what the change means for users who might read this. For formatting guidance:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
what the change means for users who might read this. For formatting guidance:
what the change means for users who might read this. For formatting guidance,

Please correct me if I'm wrong, but the : feels wrong here. Alternatively, no punctuation at all

`pre-commit`_.
``pre-commit`` compliance is automatically checked on all Iris pull requests
(more info: :ref:`pre_commit_ci`), but you can also run pre-commit locally as
Git hooks - every time you make a commit:

@ESadek-MO ESadek-MO Jun 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The punctuation feels a bit janky here, but I'm realising I may just have a bias against colons.

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