Establish CI customization variable convention - #2705
Open
rwgk wants to merge 1 commit into
Open
Conversation
Allow synchronized repositories to opt into the shared Security Suite after its prerequisites are provisioned, while preserving the canonical public behavior. Document the CI_CUSTOMIZATIONS namespace for future repository-specific workflow settings.
Contributor
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Contributor
Author
|
/ok to test |
|
rwgk
marked this pull request as ready for review
August 26, 2026 22:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Establish a
CI_CUSTOMIZATIONS_*GitHub Actions variable convention for repository-specific workflow behavior. This lets an alternative synchronized repository opt into the shared NVIDIA Security Suite after its prerequisites are provisioned, without hard-coding private repository names in the public workflow.The canonical
NVIDIA/cuda-pythonbehavior is unchanged. The newci/README.mddocuments the namespace, fail-closed default, and current Security Suite opt-in.xrefs:
Checklist