Use the Mission Control comment

Lifecycle’s Mission Control comment is a status surface and structured input. Edit only the values and checkboxes in this comment. Keep the generated headings and the syntax around them so Lifecycle can parse the result.

Select Services

The comment groups selected default Services and available optional Services. Lifecycle enables a checked item:

When possible, check or clear multiple Services in one edit. Each saved checkbox change can queue work.

Change a branch or external URL

For an editable Service, replace the value after its name:

Lifecycle checks whether the Service type accepts a branch or external URL. If it restores the previous value, examine the generated comment message and the repository configuration.

Change the Environment ID

The comment uses the historical label UUID, but the value is a human-readable Environment ID, not an RFC UUID:

IDs use 3–50 lowercase letters, numbers, and hyphens. If you change the ID, Lifecycle also changes URLs and references that contain it.

Set temporary Environment variables

Add one runtime override per line:

These values apply to this Environment and do not update lifecycle.yaml. Move a durable non-secret value into repository configuration after the test.

Request actions

The generated Actions section exposes operations supported for the current Environment, such as redeploy. Keep the action text and change only the shown checkbox or value.

An Options section appears only for settings that apply to the current Environment. For example, a configured CDN Service can expose a purge option. Default-branch tracking controls are conditional. Their presence does not mean that all Environments can enable tracking from the comment.

Edit check

After you save the comment, complete these steps:

1. Wait for Lifecycle to update the comment.
2. Make sure that Lifecycle retained the value.
3. Open the linked Environment.
4. Check the queued status.
5. Use the UI or lfc builds status <environment-id> --watch to follow the result.

If the comment does not update, see Missing pull-request comment.