From 222027b4805ae623a679385b1c1275517d6b9ee9 Mon Sep 17 00:00:00 2001 From: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> Date: Tue, 25 Nov 2025 16:45:28 +0000 Subject: [PATCH 1/2] Remove Misc/ACKS --- .github/CONTRIBUTING.rst | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/.github/CONTRIBUTING.rst b/.github/CONTRIBUTING.rst index 224061f2c5a350..082b8ee0b3d514 100644 --- a/.github/CONTRIBUTING.rst +++ b/.github/CONTRIBUTING.rst @@ -28,13 +28,10 @@ Please be aware that our workflow does deviate slightly from the typical GitHub project. Details on how to properly submit a pull request are covered in `Lifecycle of a Pull Request `_. We utilize various bots and status checks to help with this, so do follow the -comments they leave and their "Details" links, respectively. The key points of -our workflow that are not covered by a bot or status check are: - -- All discussions that are not directly related to the code in the pull request - should happen on `GitHub Issues `_. -- Upon your first non-trivial pull request (which includes documentation changes), - feel free to add yourself to ``Misc/ACKS``. +comments they leave and their "Details" links, respectively. A key point of +our workflow that is not covered by a bot or status check is that all +discussions that are not directly related to the code in the pull request +should happen on `GitHub Issues `_. Setting Expectations From 67d72ba3be782e0e66e4c7d8ee211b41afcd0237 Mon Sep 17 00:00:00 2001 From: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> Date: Tue, 25 Nov 2025 18:40:02 +0000 Subject: [PATCH 2/2] Update .github/CONTRIBUTING.rst Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- .github/CONTRIBUTING.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/.github/CONTRIBUTING.rst b/.github/CONTRIBUTING.rst index 082b8ee0b3d514..94b67ce3dbe341 100644 --- a/.github/CONTRIBUTING.rst +++ b/.github/CONTRIBUTING.rst @@ -28,10 +28,12 @@ Please be aware that our workflow does deviate slightly from the typical GitHub project. Details on how to properly submit a pull request are covered in `Lifecycle of a Pull Request `_. We utilize various bots and status checks to help with this, so do follow the -comments they leave and their "Details" links, respectively. A key point of -our workflow that is not covered by a bot or status check is that all -discussions that are not directly related to the code in the pull request -should happen on `GitHub Issues `_. +comments they leave and their "Details" links, respectively. + +The final key part of our workflow is that all discussions that are not +directly related to the code in the pull request should happen on +`GitHub Issues `__, generally in the +pull request's parent issue. Setting Expectations