This is an automated email from the ASF dual-hosted git repository.
hubcio pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iggy.git
The following commit(s) were added to refs/heads/master by this push:
new 2a7192ee5 ci: auto-assign issue authors who volunteer to contribute
(#3400)
2a7192ee5 is described below
commit 2a7192ee58ac93e5e1fd8c0d0ab778ce8ee25150
Author: Hubert Gruszecki <[email protected]>
AuthorDate: Mon Jun 1 13:57:54 2026 +0200
ci: auto-assign issue authors who volunteer to contribute (#3400)
---
...ssue-labeler.yml => issue-labeler-assigner.yml} | 62 +++++++++++++++++-----
.github/workflows/pr-triage-apply.yml | 1 +
CONTRIBUTING.md | 4 --
3 files changed, 51 insertions(+), 16 deletions(-)
diff --git a/.github/workflows/issue-labeler.yml
b/.github/workflows/issue-labeler-assigner.yml
similarity index 56%
rename from .github/workflows/issue-labeler.yml
rename to .github/workflows/issue-labeler-assigner.yml
index 8b70c3249..17de263e9 100644
--- a/.github/workflows/issue-labeler.yml
+++ b/.github/workflows/issue-labeler-assigner.yml
@@ -15,20 +15,29 @@
# specific language governing permissions and limitations
# under the License.
-name: Issue Labeler
+name: Issue Labeler / Assigner
-# Maps the "Affected area / component" dropdown from the bug/feature issue
-# forms (.github/ISSUE_TEMPLATE/) onto real repo labels, so reporters who
-# lack triage permission still get their issue categorized at creation.
+# Two add-only triage steps that run when a reporter opens or edits an issue:
#
-# Add-only by design: it never removes labels. Reporters rarely deselect,
-# and removing would fight maintainers who labeled by hand. addLabels is
-# idempotent, so re-running on `edited` is harmless.
+# 1. Label: maps the "Affected area / component" dropdown from the bug/feature
+# issue forms (.github/ISSUE_TEMPLATE/) onto real repo labels, so reporters
+# who lack triage permission still get their issue categorized at creation.
#
-# SECURITY: the issue body is attacker-controlled text, but it is parsed
-# only for exact matches against the fixed AREA_LABELS allowlist below, so
-# the only labels this workflow can ever apply are the ones listed here.
-# No checkout, no exec of issue contents, no token export.
+# 2. Assign: if the reporter ticked the "Contribution" checkbox ("I'm willing
+# to submit a pull request ..."), assign the issue to its author so the
+# volunteer is on record. addAssignees is idempotent and issue authors are
+# always assignable, even as outside contributors.
+#
+# Add-only by design: neither step removes anything. Reporters rarely deselect,
+# and removing would fight maintainers who labeled or reassigned by hand. Both
+# API calls are idempotent, so re-running on `edited` is harmless.
+#
+# SECURITY: the issue body is attacker-controlled text. The label step parses
+# it only for exact matches against the fixed AREA_LABELS allowlist below. The
+# assign step uses the body only as a boolean gate; the assignee comes from the
+# trusted `payload.issue.user.login`, never from body content, so the body
+# cannot inject an assignee. No checkout, no exec of issue contents, no token
+# export.
on:
issues:
@@ -39,7 +48,7 @@ permissions:
contents: read
jobs:
- label:
+ triage:
runs-on: ubuntu-24.04-arm
timeout-minutes: 5
steps:
@@ -103,3 +112,32 @@ jobs:
issue_number: context.payload.issue.number,
labels,
});
+
+ - name: Assign author who volunteered to contribute
+ uses: actions/github-script@v9
+ with:
+ script: |
+ // The "Contribution" checkbox in both issue forms renders as a
+ // task-list line. Checked, it reads `- [x] I'm willing to submit a
+ // pull request ...`; the tail differs per template (bug: "to fix
+ // this bug", feature: "to implement this feature"), so match the
+ // shared prefix only.
+ const body = context.payload.issue.body || '';
+ const volunteered =
+ /(^|\n)\s*-\s*\[[xX]\]\s+I'm willing to submit a pull
request/.test(body);
+ if (!volunteered) {
+ core.info('author did not volunteer to contribute, nothing to
assign');
+ return;
+ }
+
+ // Assignee is the trusted author from the event payload, never the
+ // body. addAssignees is a no-op if already assigned and silently
+ // ignores non-assignable users; issue authors are always
assignable.
+ const author = context.payload.issue.user.login;
+ core.info(`assigning volunteering author: ${author}`);
+ await github.rest.issues.addAssignees({
+ owner: context.repo.owner,
+ repo: context.repo.repo,
+ issue_number: context.payload.issue.number,
+ assignees: [author],
+ });
diff --git a/.github/workflows/pr-triage-apply.yml
b/.github/workflows/pr-triage-apply.yml
index 2fa172c7a..3c5e7e6b1 100644
--- a/.github/workflows/pr-triage-apply.yml
+++ b/.github/workflows/pr-triage-apply.yml
@@ -226,6 +226,7 @@ jobs:
'Slash commands (own line, regular comment) move it around the
queue:',
'',
'- `/ready` - back to `S-waiting-on-review` after addressing
feedback',
+ '- `/author` - flip to `S-waiting-on-author` while you finish
changes',
'- `/request-review @user-or-team` - request a reviewer',
'',
'See
[CONTRIBUTING.md](https://github.com/apache/iggy/blob/master/CONTRIBUTING.md#pr-triage-commands)
for details.',
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 98155d8cd..99e4e6da7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -10,10 +10,6 @@ PRs without one may be closed at maintainer's discretion.
- Maintainer may request for more details or a different approach
3. Then code
-## Size Limits
-
-For new contributors we require to keep PRs under 500 lines of code, unless
explicitly approved by a maintainer under linked issue.
-
## High-Risk Areas
These require design discussion in the issue before coding:
