Skip to content

trac and ticket keyword blat - #480

Merged
Jenny Hickson (jennyhickson) merged 21 commits into
MetOffice:github_wpsfrom
james-bruten-mo:keyword_flush
Oct 24, 2025
Merged

trac and ticket keyword blat#480
Jenny Hickson (jennyhickson) merged 21 commits into
MetOffice:github_wpsfrom
james-bruten-mo:keyword_flush

Conversation

@james-bruten-mo

Copy link
Copy Markdown
Contributor

Removes examples of ticket and trac from working practices

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I've tried to deal with line lengths in my suggestions. Lots of trivial comments...

Comment thread source/Development/inputs.rst Outdated
Comment thread source/Development/inputs.rst
Comment on lines +6 to +10
Multi-repository changes are expected to pass the regression tests for all the
repositories involved. To carry out the tests involved in a linked ticket it
can be helpful to refer to the :ref:`repository figure <multirepo>`; testing
both child and parent repositories as needed. Further details of how testing
in each repository is handled can be found on the :ref:`Testing
page<testing>`.
repositories involved. To carry out the tests involved in a linked PR it can be
helpful to refer to the :ref:`repository figure <multirepo>`; testing both child
and parent repositories as needed. Further details of how testing in each
repository is handled can be found on the :ref:`Testing page<testing>`.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Multi-repository changes are expected to pass the regression tests for all the
repositories involved. To carry out the tests involved in a linked ticket it
can be helpful to refer to the :ref:`repository figure <multirepo>`; testing
both child and parent repositories as needed. Further details of how testing
in each repository is handled can be found on the :ref:`Testing
page<testing>`.
repositories involved. To carry out the tests involved in a linked PR it can be
helpful to refer to the :ref:`repository figure <multirepo>`; testing both child
and parent repositories as needed. Further details of how testing in each
repository is handled can be found on the :ref:`Testing page<testing>`.
Multi-repository changes are expected to pass the regression tests for all the
repositories involved. To carry out the tests involved in a linked pull request it
can be helpful to refer to the :ref:`repository figure <multirepo>`; testing both
child and parent repositories as needed. Further details of how testing in each
repository is handled can be found on the :ref:`Testing page<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.

Done

Comment thread source/Development/TestSuites/ukca.rst Outdated
Comment thread source/Development/kgo.rst Outdated
Comment thread source/FurtherDetails/glossary.rst Outdated
Comment thread source/FurtherDetails/glossary.rst Outdated
Comment thread source/FurtherDetails/glossary.rst
Comment thread source/FurtherDetails/who.rst Outdated
Comment thread source/FurtherDetails/who.rst Outdated
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>

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.

Thanks, all done

Comment on lines +6 to +10
Multi-repository changes are expected to pass the regression tests for all the
repositories involved. To carry out the tests involved in a linked ticket it
can be helpful to refer to the :ref:`repository figure <multirepo>`; testing
both child and parent repositories as needed. Further details of how testing
in each repository is handled can be found on the :ref:`Testing
page<testing>`.
repositories involved. To carry out the tests involved in a linked PR it can be
helpful to refer to the :ref:`repository figure <multirepo>`; testing both child
and parent repositories as needed. Further details of how testing in each
repository is handled can be found on the :ref:`Testing page<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.

Done

Comment thread source/Development/inputs.rst
Comment thread source/Development/planning_your_change.rst
Comment thread source/FurtherDetails/glossary.rst Outdated
Comment on lines +17 to +21
A technical review of the changes involved in the PR, including checks
that code standards have been upheld and that the working practices have
been followed. These reviews are generally completed by a member of the
Simulation Systems and Deployment Team. Once a review has been approved
the Code Systems Reviewer is then responsible for committing the change to
the trunk.

..
or the Core Capability Development Team (for LFRic only reviews).
Simulation IT Team. Once a review has been approved the Code Systems
Reviewer is then responsible for committing the change to the trunk.

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.

Done

Comment thread source/FurtherDetails/glossary.rst
@jennyhickson
Jenny Hickson (jennyhickson) merged commit f74a702 into MetOffice:github_wps Oct 24, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants