From b367022f2710e2fb1db593fe133579788da586cc Mon Sep 17 00:00:00 2001 From: Kevin Christian Amparado Date: Sun, 5 Oct 2025 10:57:03 +0800 Subject: [PATCH 1/5] remove "issue_assign" job on github actions --- .github/workflows/comment-commands.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/.github/workflows/comment-commands.yml b/.github/workflows/comment-commands.yml index e31d9ab343459..d407f40ef2c08 100644 --- a/.github/workflows/comment-commands.yml +++ b/.github/workflows/comment-commands.yml @@ -9,15 +9,6 @@ permissions: pull-requests: write jobs: - issue_assign: - runs-on: ubuntu-24.04 - if: (!github.event.issue.pull_request) && github.event.comment.body == 'take' - concurrency: - group: ${{ github.actor }}-issue-assign - steps: - - run: | - echo "Assigning issue ${{ github.event.issue.number }} to ${{ github.event.comment.user.login }}" - curl -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" -d '{"assignees": ["${{ github.event.comment.user.login }}"]}' https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees preview_docs: runs-on: ubuntu-24.04 if: github.event.issue.pull_request && github.event.comment.body == '/preview' From fd698886ba3b93446e43f50cd05fd54203963783 Mon Sep 17 00:00:00 2001 From: Kevin Christian Amparado Date: Sun, 5 Oct 2025 11:02:17 +0800 Subject: [PATCH 2/5] update contributing doc --- doc/source/development/contributing.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/source/development/contributing.rst b/doc/source/development/contributing.rst index 66178a88e3e31..0f78d653c2011 100644 --- a/doc/source/development/contributing.rst +++ b/doc/source/development/contributing.rst @@ -36,13 +36,13 @@ and `good first issue `_ are typically good for newer contributors. -Once you've found an interesting issue, it's a good idea to assign the issue to yourself, -so nobody else duplicates the work on it. On the Github issue, a comment with the exact -text ``take`` to automatically assign you the issue -(this will take seconds and may require refreshing the page to see it). +Once you've found an interesting issue, leave a comment with your idea of +how you plan to approach it, and start working on it. If somebody else has +already said they'd be working on the issue in the past 2-3 weeks, please let +them finish their work, otherwise consider it stalled and take it over. If for whatever reason you are not able to continue working with the issue, please -unassign it, so other people know it's available again. You can check the list of +leave a comment on an issue, so other people know it's available again. You can check the list of assigned issues, since people may not be working in them anymore. If you want to work on one that is assigned, feel free to kindly ask the current assignee if you can take it (please allow at least a week of inactivity before considering work in the issue discontinued). From cad305f04b03b718644002b36a374d7084ae4196 Mon Sep 17 00:00:00 2001 From: Kevin Amparado <109636487+KevsterAmp@users.noreply.github.com> Date: Mon, 6 Oct 2025 19:41:26 +0800 Subject: [PATCH 3/5] Update doc/source/development/contributing.rst Co-authored-by: Matthew Roeschke <10647082+mroeschke@users.noreply.github.com> --- doc/source/development/contributing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/development/contributing.rst b/doc/source/development/contributing.rst index 0f78d653c2011..be2c2b931c628 100644 --- a/doc/source/development/contributing.rst +++ b/doc/source/development/contributing.rst @@ -36,8 +36,8 @@ and `good first issue `_ are typically good for newer contributors. -Once you've found an interesting issue, leave a comment with your idea of -how you plan to approach it, and start working on it. If somebody else has +Once you've found an interesting issue, leave a comment with your intention +to start working on it. If somebody else has already said they'd be working on the issue in the past 2-3 weeks, please let them finish their work, otherwise consider it stalled and take it over. From 9affc402281c885d809ca19eaf792537aa24fd3d Mon Sep 17 00:00:00 2001 From: Kevin Amparado <109636487+KevsterAmp@users.noreply.github.com> Date: Mon, 6 Oct 2025 19:41:43 +0800 Subject: [PATCH 4/5] Update doc/source/development/contributing.rst Co-authored-by: Matthew Roeschke <10647082+mroeschke@users.noreply.github.com> --- doc/source/development/contributing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/development/contributing.rst b/doc/source/development/contributing.rst index be2c2b931c628..ad7c074621021 100644 --- a/doc/source/development/contributing.rst +++ b/doc/source/development/contributing.rst @@ -38,8 +38,8 @@ are typically good for newer contributors. Once you've found an interesting issue, leave a comment with your intention to start working on it. If somebody else has -already said they'd be working on the issue in the past 2-3 weeks, please let -them finish their work, otherwise consider it stalled and take it over. +already commented on issue but they have shown a lack of activity in the issue +or a pull request in the past 2-3 weeks, you may take it over. If for whatever reason you are not able to continue working with the issue, please leave a comment on an issue, so other people know it's available again. You can check the list of From 0a098c119ea974ecab2a3c01a49bb2921210da93 Mon Sep 17 00:00:00 2001 From: Kevin Christian Amparado Date: Mon, 6 Oct 2025 19:43:18 +0800 Subject: [PATCH 5/5] remove redundant line on contributing.rst --- doc/source/development/contributing.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/source/development/contributing.rst b/doc/source/development/contributing.rst index ad7c074621021..a49afce8861cc 100644 --- a/doc/source/development/contributing.rst +++ b/doc/source/development/contributing.rst @@ -43,9 +43,7 @@ or a pull request in the past 2-3 weeks, you may take it over. If for whatever reason you are not able to continue working with the issue, please leave a comment on an issue, so other people know it's available again. You can check the list of -assigned issues, since people may not be working in them anymore. If you want to work on one -that is assigned, feel free to kindly ask the current assignee if you can take it -(please allow at least a week of inactivity before considering work in the issue discontinued). +assigned issues, since people may not be working in them anymore. We have several :ref:`contributor community ` communication channels, which you are welcome to join, and ask questions as you figure things out. Among them are regular meetings for