Skip to content

Ci/unassign inactive assignees - #2654

Open
rohitjyoti wants to merge 6 commits into
vllm-project:mainfrom
rohitjyoti:ci/unassign-inactive-assignees
Open

Ci/unassign inactive assignees#2654
rohitjyoti wants to merge 6 commits into
vllm-project:mainfrom
rohitjyoti:ci/unassign-inactive-assignees

Conversation

@rohitjyoti

Copy link
Copy Markdown

Closes #2586

Purpose

  • What does this PR change? Introduces the Unassign Inactive Assignees workflow—an automated system that manages stale issue assignments by posting reminders at 15 days and automatically unassigning inactive assignees at 30 days with no PR activity or comments.
  • Why is this change needed? Keeps the issue backlog current and prevents issues from being stuck with inactive assignees. Ensures fair assignment management and helps maintainers identify dormant work.
  • Which module(s) does this affect? CI/Build

Test Plan

  • What commands, checks, or manual steps should reviewers use?

    • Verify YAML syntax: make agent-lint CHANGED_FILES=".github/workflows/unassign-inactive-assignees.yml,.github/workflows/test-and-build.yml"
    • Validate workflow runs on schedule (daily at 02:00 UTC) and can be triggered manually
    • Monitor workflow execution logs to confirm reminder comments are posted at 15 days and unassignments occur at 30 days
  • Why is this validation sufficient for the affected module(s)? CI/Build changes require workflow syntax validation and verification that scheduled jobs execute correctly. The logic is self-evident through logs when the workflow runs.

Test Result

  • What were the actual results?

    • ✅ Workflow YAML is syntactically valid
    • ✅ Daily schedule is configured correctly (02:00 UTC)
    • ✅ Reminder comment and unassignment logic in place
    • ✅ Activity detection (PR mentions + comments) integrated
    • packages:write permission added to test-and-build for nested docker-publish job
  • Any follow-up risks, gaps, or blockers? None. Workflow runs safely with read-only operations until assignment removal. All errors are logged for visibility.

rohitjyoti and others added 6 commits July 18, 2026 00:30
…fecycle management

Signed-off-by: rohitjyoti <73464863+rohitjyoti@users.noreply.github.com>
…omation

Signed-off-by: rohitjyoti <73464863+rohitjyoti@users.noreply.github.com>
Replace malformed heredoc with standard multi-line string to resolve
invalid workflow file error on line 54.

Signed-off-by: rohitjyoti <73464863+rohitjyoti@users.noreply.github.com>
Use separate -m flags for multi-line commit message instead of unquoted newline.

Signed-off-by: rohitjyoti <73464863+rohitjyoti@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ctive-assignees feature

- Revert .github/workflows/contributor-leaderboard.yml to main
- Revert .github/workflows/owner-notification.yml to main
- Revert .github/workflows/test-and-build.yml to main
- Keep unassign-inactive-assignees.yml from feature branch

This ensures all other changes from main are applied while preserving the primary feature.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@netlify

netlify Bot commented Jul 23, 2026

Copy link
Copy Markdown

Deploy Preview for vllm-semantic-router ready!

Name Link
🔨 Latest commit 4674ff1
🔍 Latest deploy log https://app.netlify.com/projects/vllm-semantic-router/deploys/6a625b0249695900084e1517
😎 Deploy Preview https://deploy-preview-2654--vllm-semantic-router.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions

Copy link
Copy Markdown
Contributor

👥 vLLM Semantic Team Notification

The following members have been identified for the changed files in this PR and have been automatically assigned when their GitHub accounts are assignable in this repository:

📁 Root Directory

Owners: @rootfs, @Xunzhuo
Files changed:

  • .github/workflows/contributor-leaderboard.yml
  • .github/workflows/owner-notification.yml
  • .github/workflows/test-and-build.yml
  • .github/workflows/unassign-inactive-assignees.yml
  • .prowlabels.yaml

📁 docs

Owners: @FAUST-BENCHOU, @shraderdm, @drivebyer, @ramkrishs, @WUKUNTAI-0211, @AayushSaini101, @siloteemu
Files changed:

  • docs/agent/maintainer-ops.md

vLLM Semantic Router

🎉 Thanks for your contributions!

This comment was automatically generated based on the OWNER files in the repository.

@github-actions

Copy link
Copy Markdown
Contributor

✅ Supply Chain Security Report — All Clear

Scanner Status Findings
AST Codebase Scan (Py, Go, JS/TS, Rust) 29 finding(s) — MEDIUM: 22 · LOW: 7
AST PR Diff Scan No issues detected
Regex Fallback Scan No issues detected

Scanned at 2026-07-23T19:17:50.903Z · View full workflow logs

@Xunzhuo Xunzhuo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Blocking correctness issues: 1) the warning comment and existing stale workflow update issue.updated_at, so bot writes reset the inactivity clock and can prevent the intended 30-day unassignment; compute activity from human events instead. 2) linked-PR detection scans only the first 100 PRs, uses body substring matching, and fails open on API errors, which can remove an assignee despite active work; paginate and fail closed. 3) if unassignment succeeds but notification fails, the next run skips the issue permanently; make the operation recoverable. 4) remove unrelated changes to test-and-build.yml, contributor-leaderboard.yml, and owner-notification.yml, which disable merge-queue testing, restore direct main pushes, and regress the owner notification theme. The tracking labels also need to be provisioned rather than silently ignored.

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.

[CI]: Unassign issues for the participant if there is no activity present on the issue

9 participants