Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 11 additions & 7 deletions content/cli/lavaflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -262,10 +262,13 @@ Fix:

### Allow ungated workflows

By default, LavaFlow doesn't open a fix's pull request where a workflow in
the repository could run it, or put its text into a command, with the
repository's secrets before a person approves it: the fix stays on its run
instead. Only the project's owner can turn that on, signed in as a person:
Allow normal repository CI for initial PRs a person merges when the project's `lavaflow.repository_ci` capability is available.
This is the same permission as **Allow repository CI** in the dashboard's LavaFlow settings.
It changes only this permission; autonomy, Code Quality, and merge settings stay as they are.
See [Review and merge fixes yourself](/platform/guides/lavaflow#review-and-merge-fixes-yourself).

On the guarded publication path, this permission instead allows a PR to open past workflows that could use repository secrets before human approval.
Only the project's owner can turn it on, signed in as a person:
with `volcano login`, or another platform token that expires. It applies to the
repository the project is connected to now, while their GitHub account can push
to it:
Expand All @@ -280,9 +283,10 @@ reviews them. LavaFlow writes those changes from the project's error logs,
which its users can influence. Turn it on only if those workflows keep secrets
away from untrusted code; gating them on a label a person adds is safer.

Connecting the project to another repository, or disconnecting it, turns the
setting off, and connecting the first repository again doesn't turn it back
on.
Changing the connected repository or GitHub installation, or disconnecting it, turns the setting off.
Changing back does not restore permission.
An existing grant stays on otherwise; a saved `false` stays false.
Turning it off stops later publication writes and retries from using normal CI, while existing PRs and CI already started remain.

`settings set` prints that warning and asks before it turns the setting on.
`--yes` skips the question but still prints the warning, on stderr, so
Expand Down
11 changes: 8 additions & 3 deletions content/platform/api-reference/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -204,6 +204,7 @@ curl "https://api.volcano.dev/capabilities"
{ "id": "lavaflow.merge", "status": "unavailable" },
{ "id": "lavaflow.lineage", "status": "unavailable" },
{ "id": "lavaflow.open_pr_ci_start", "status": "unavailable" },
{ "id": "lavaflow.repository_ci", "status": "unavailable" },
{ "id": "lavaflow.slack", "status": "unavailable" },
{ "id": "lavaflow.aikido", "status": "unavailable" },
{ "id": "functions.response_streaming", "status": "available" },
Expand All @@ -227,7 +228,8 @@ curl "https://api.volcano.dev/capabilities"
| `lavaflow` | LavaFlow, which diagnoses a project's issues, opens pull requests that fix them, and can merge them. This list says only whether it's released in the environment; a project's list says whether that project has it |
| `lavaflow.merge` | Letting LavaFlow [merge its fixes](../guides/lavaflow.md#merge-fixes): `autonomy: merge` and changing `merge_policy`; reading merges works either way |
| `lavaflow.lineage` | LavaFlow [following up its fixes](../guides/lavaflow.md#fix-lineage): follow-up runs and the lineage holds; lineage fields already stored read either way |
| `lavaflow.open_pr_ci_start` | A fix you [review and merge yourself](../guides/lavaflow.md#review-and-merge-fixes-yourself) opening ready for review, with LavaFlow running its CI once unless your repository may run CI outside GitHub Actions; unavailable, it opens as a draft whose commit skips CI |
| `lavaflow.open_pr_ci_start` | Compatibility capability for normal repository CI or the earlier one-time CI start. Availability grants no repository permission. See [Review and merge fixes yourself](../guides/lavaflow.md#review-and-merge-fixes-yourself) |
| `lavaflow.repository_ci` | Normal CI on initial PRs a person merges. The owner must also [allow it for the connected repository](../guides/lavaflow.md#allow-ungated-workflows); availability alone does not authorize execution |
| `lavaflow.slack` | [Reporting problems from Slack](../guides/lavaflow-slack.md): installing Volcano's Slack app, connecting Slack accounts, the channel picker, and binding channels; reading and removing connections and bindings work either way |
| `lavaflow.aikido` | [Fixing Aikido issues](../guides/lavaflow-aikido.md): connecting an Aikido workspace and binding projects to it; reading and removing connectors and bindings work either way |
| `functions.response_streaming` | [Streaming a response](../functions/invoking-functions.md#stream-a-response) on a function's own URL |
Expand Down Expand Up @@ -289,8 +291,11 @@ says what the project can still do:
`lavaflow.merge` is `available` when `lavaflow` is and LavaFlow may merge
fixes in the environment. `lavaflow.lineage` is `available` when `lavaflow` is
and fix lineage is released in the environment. `lavaflow.open_pr_ci_start`
is `available` when `lavaflow` is and the one CI start for fixes you merge is
released in the environment. `lavaflow.slack` is
is `available` when `lavaflow` is and normal repository CI or the earlier one-time CI-start path is released in the environment.
`lavaflow.repository_ci` reports normal-CI availability specifically.
Normal publication also requires the owner's saved `allow_ungated_workflows: true` permission for the connected repository and installation.
Neither capability grants that permission; without it, the guarded publication policy still applies.
Read the PR description as explained under [Review and merge fixes yourself](../guides/lavaflow.md#review-and-merge-fixes-yourself). `lavaflow.slack` is
`available` when `lavaflow` is and reporting problems from Slack is available
in the environment, which is rolling out environment by environment.
`lavaflow.aikido` is `available` when `lavaflow` is and Aikido reports have
Expand Down
Loading
Loading