Skip to content

Conversation

@Steboss
Copy link
Collaborator

@Steboss Steboss commented Jan 8, 2026

No description provided.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Greptile Overview

Greptile Summary

This PR adds the GitHub user Steboss to the authorization list in the nvfuser-ci-trigger workflow. This allows Steboss to trigger CI builds on self-hosted infrastructure using !build or !test commands on pull requests.

Changes:

  • Added github.actor == 'Steboss' to the authorization condition in .github/workflows/nvfuser-ci-trigger.yml

Notes:

  • The change follows the established pattern of adding authorized users
  • The PR author matches the username being added (Steboss)
  • The formatting and indentation are consistent with existing entries

Confidence Score: 5/5

  • This PR is safe to merge with no risks
  • This is a simple authorization list update that follows the exact pattern used for all other authorized users. The change is syntactically correct, properly formatted, and adds no new logic or complexity. It only extends the existing authorization list with one additional GitHub username.
  • No files require special attention

Important Files Changed

File Analysis

Filename Score Overview
.github/workflows/nvfuser-ci-trigger.yml 5/5 Added Steboss to authorized users list for triggering CI jobs via comments

Sequence Diagram

sequenceDiagram
    participant User as Authorized User
    participant GitHub as GitHub
    participant Auth as Authorization Job
    participant Vuln as Vulnerability Scan
    participant CI as CI Job Trigger
    
    User->>GitHub: Comment with !build or !test
    GitHub->>Auth: Trigger issue_comment event
    Auth->>Auth: Check if actor in authorized list
    Note over Auth: Now includes Steboss
    Auth->>Auth: Run blossom-ci authorization
    Auth->>Vuln: Pass authorization outputs
    Vuln->>Vuln: Checkout code and scan
    Vuln->>CI: Trigger CI job
    CI->>CI: Start CI job on infrastructure
Loading

@xwang233
Copy link
Collaborator

xwang233 commented Jan 8, 2026

!build

@xwang233 xwang233 added enable-auto-merge Auto-merge a PR when: 1) PR mergeable 2) Internal CI complete 3) No failures and removed enable-auto-merge Auto-merge a PR when: 1) PR mergeable 2) Internal CI complete 3) No failures labels Jan 8, 2026
@xwang233 xwang233 merged commit 64efede into NVIDIA:main Jan 8, 2026
20 of 21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enable-auto-merge Auto-merge a PR when: 1) PR mergeable 2) Internal CI complete 3) No failures

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants