Actions

Open a repository's Actions tab to inspect its workflows and runs. Execution features depend on the deployment. A workflow can pass validation and have a run record even when no hosted runner can execute its jobs.

Add a workflow

Workflow files live in .github/workflows/ with a .yml or .yaml extension. Commit changes to the repository and inspect the workflow's validation result in Actions. The platform accepts a bounded subset of GitHub Actions syntax; it does not promise that every existing GitHub workflow will run unchanged.

This small workflow illustrates the source format:

name: Test
on:
  workflow_dispatch:
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Workflow reached the runner"

Use a runner label offered by your deployment. This example does not check out your repository or install dependencies. Confirm that the workflow can execute before using it as a release gate. Start with a disposable repository and avoid adding credentials to workflow source.

Inspect a run

Choose a run to see its status, jobs, and available logs. Check the selected ref and commit before diagnosing a failure. A queued run may be waiting for capacity or an eligible runner, while a rejected workflow needs a source or permission correction.

With an authenticated GBB CLI, inspect the commands offered by your installed version:

gbb actions --help
gbb actions run --help

Dispatch, cancel, or rerun

Manual dispatch is available for workflows that declare workflow_dispatch and pass the deployment's validation and authorization checks. Use the workflow's configured input types and select the intended branch or tag. Canceling or rerunning also requires permission; a rerun is a new execution attempt, not a repair of the old logs.

Integrations can use the workflow and run operations in the API endpoint reference. Preserve the request identity required by each operation when retrying after a lost response.

Protect workflow credentials

Use repository or environment secret controls provided by your administrator. Keep raw credentials out of YAML, issue bodies, artifacts, and log output. Log masking can miss secret values.

If no eligible execution capability is offered, ask the deployment administrator which runner features and workflow syntax are enabled. See Troubleshooting for information to include without disclosing secrets.