rebase workspace

List, switch, create, and manage members of the Rebase workspaces you belong to.

Synopsis

rebase workspace
rebase workspace compute-policy show [--json]
rebase workspace compute-policy set [--max-run-timeout-seconds <s>] [--max-job-timeout-seconds <s>] [--max-concurrent-runs <n>] [--max-instances <n>] [--max-concurrency <n>] [--max-cpu-milli <milli>] [--max-memory-mib <mib>] [--json]
rebase workspace create [workspace] [--workspace-name <name>]
rebase workspace invite [<email-or-github-username>] [--email <email>] [--github <username>] [--role Viewer|Developer|Admin|Owner]
rebase workspace list
rebase workspace members
rebase workspace members --json
rebase workspace notifications show
rebase workspace notifications set --webhook-url <url> --webhook-secret <secret> --on-failure
rebase workspace set-role <target> --role Viewer|Developer|Admin|Owner [--json]
rebase workspace switch <workspace>
rebase workspace uninvite <target>

Subcommands

SubcommandArgumentsDescription
nonenoneList the workspaces you belong to and show which one is selected.
compute-policyshow / setRead or change the workspace's compute ceilings — service request timeout, job run timeout, concurrent runs, instances, per-instance concurrency, and the per-target max_cloud_run_cpu_milli / max_cloud_run_memory_mib. Reading is open to any member; raising a ceiling requires a superadmin, who targets another workspace with the global --workspace flag. See Workflow Execution.
create[workspace]Create a new workspace and save it as a local profile.
invite[<email-or-github-username>]Invite a person to the active workspace by email address or GitHub username. Passing both --email and --github puts both on one invite, so it binds to whichever identity the person signs in with first. --role defaults to Viewer.
listnoneList the workspaces you belong to and show which one is selected.
membersnoneList active members and pending invites with their roles.
notificationsshow / setConfigure run failure notifications (webhook URL, HMAC secret, on/off). See Failure Alerting.
set-role<target>Change an existing member's role with --role/-r. <target> is the member's email, GitHub username, or profile id. Requires members:write (Owner or Admin); only an Owner can assign the Owner role or modify another Owner, and the last active Owner cannot be demoted.
switch<workspace>Switch the active workspace to one you belong to, by name or id, keeping the current profile.
uninvite<target>Revoke a pending invite by email, GitHub username, or invite id. The person can be invited again later; an accepted invite is a membership, managed with set-role.
usagenoneHidden alias for rebase usage, kept for older scripts.

Notifications

rebase workspace notifications set \
  --webhook-url https://hooks.example.com/rebase \
  --webhook-secret <secret> \
  --on-failure
rebase workspace notifications show
rebase workspace notifications set --no-on-failure   # disable
rebase workspace notifications set --clear-webhook   # remove URL and secret

notifications set also takes --on-stale / --no-on-stale to turn stale dataset notifications on or off, and --email/-e / --no-email to email the owner of a scheduled workflow when it starts failing and again when it recovers.

The webhook receives a signed run.failed payload whenever a run in the workspace fails; see Failure Alerting for the payload and signature verification.

Roles

Workspace roles are Viewer, Developer, Admin, and Owner. Use Developer for collaborator/editor access:

rebase workspace invite davide@rebase.energy --role Developer

Pending invites can be updated by running rebase workspace invite again for the same email address or GitHub username with a new role.

On this page