Spaces:

Wauplin
/

gradio-space-ci

Running

App Files Files Community

Should CI spaces be private to prevent exposing code on private spaces?

by mrfakename - opened Feb 27

base: refs/heads/main

←

from: refs/pr/4

Discussion Files changed

-0

mrfakename

Feb 27

No description provided.

Should CI spaces be private to prevent exposing code on private spaces?36719993

Wauplin

Owner Feb 27

Following the creation of this PR, an ephemeral Space Wauplin/gradio-space-ci-ci-pr-4 has been started. Any changes pushed to this PR will be synced with the test Space.
Since this PR has not been created by a trusted author, the ephemeral Space has not been configured with the correct hardware, storage, and secrets. An admin must configure it manually.
(This is an automated message.)

Wauplin

Owner Feb 27

Private Spaces would be deployed as private while public ones will stay public. That's the default behavior at least (see here). Default behavior can be overwritten by passing private=True to configure_space_ci here.

Wauplin changed pull request status to closed Feb 27

Wauplin

Owner Feb 27

PR is now merged/closed. The ephemeral Space has been deleted.
(This is an automated message.)

Upload images, audio, and videos by dragging in the text input, pasting, or clicking here.

Tap or paste here to upload images

· Sign up or log in to comment