Skip to content

feat(ci): opt into OSRB License Risk Triage workflow - #3

Closed
dhaval2025 wants to merge 1 commit into
NVIDIA:mainfrom
dhaval2025:add-osrb-license-check
Closed

dhaval2025 wants to merge 1 commit into
NVIDIA:mainfrom
dhaval2025:add-osrb-license-check

Conversation

@dhaval2025

Copy link
Copy Markdown

Summary

Adds .github/workflows/osrb.yml to opt this repo into the OSRB License Risk Triage GitHub Action (NVIDIA-Omniverse/sectools-skills@v1).

After this lands, future PRs to main opened by NVIDIA-org contributors get:

  • A sticky PR comment with license-risk verdict (Tier 0–4)
  • A rendered verdict in the Actions tab Job Summary
  • An osrb-out/ artifact bundle (OSRB packet, NVBug draft, written source offer when applicable)
  • A gate on Tier 1a/1b copyleft / high-risk licenses

Running in advisory-only mode (gate-on-high: 'false') during initial adoption — the comment posts but the gate never blocks the merge. Flip to 'true' once known high-risk deps are resolved.

⚠️ This PR does not exercise the workflow itself

Two GitHub-fundamental reasons:

  1. New workflow files on fork-PR head branches don't auto-trigger. GitHub security model. The workflow starts running after this PR is merged.
  2. Fork PRs can't fetch internal reusable workflows. sectools-skills is internal-visibility within the NVIDIA enterprise; the GITHUB_TOKEN on a fork PR doesn't carry enterprise auth.

Once merged, all PRs to main opened from branches within the nvidia or NVIDIA-Omniverse orgs will trigger OSRB triage normally. External-contributor (non-NVIDIA) fork PRs will silently skip the OSRB job — those changes require manual OSRB review by a maintainer at merge time.

Pre-merge verification

If you want to confirm the workflow actually runs before merging, the cleanest way is:

  1. Merge this PR (the workflow file lands on main)
  2. Open a follow-up PR from a branch in nvidia/simready-foundation (not a fork) with any trivial change
  3. Watch the OSRB License Risk Triage / triage / triage and … / triage / comment checks fire on that PR

Reference

🤖 Generated with Claude Code

Adds the 6-line OSRB triage workflow from
NVIDIA-Omniverse/sectools-skills@v1. Running in advisory-only mode
(gate-on-high: 'false') during initial adoption — the PR comment
and Job Summary land on every PR, but the gate never blocks merge.

Note: this workflow only runs for PRs opened from branches within
the NVIDIA enterprise (i.e., from the nvidia or NVIDIA-Omniverse
orgs). External-contributor fork PRs cannot fetch the
internal-visibility reusable workflow and will silently skip the
OSRB job. Filing nspect/OSRB review for those changes remains a
manual maintainer action.
@dhaval2025

Copy link
Copy Markdown
Author

Closing — opening this on the internal mirror instead, where the reusable workflow's enterprise-visibility works natively (no fork-PR auth limitation).

@dhaval2025 dhaval2025 closed this May 21, 2026
@dhaval2025
dhaval2025 deleted the add-osrb-license-check branch May 21, 2026 06:47
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.

1 participant