Review, Merge, and Deploy

Validate pull requests, synchronize protected main, and deploy with Git provenance

Workflow-level Git authoring is paused in code, with no environment opt-in. This guide is retained as a reference for the legacy implementation; its authoring controls are unavailable. Existing protection and workspace synchronization remain enforced. Use workspace capture to review all active workflows together.

To review every workflow together, use workspace capture, review, commit, and PR creation.

Source Control keeps Git review and runtime deployment deliberately separate. This makes it possible to approve a workflow definition without changing production until the synchronized main draft is ready.

Open the Pull Request

For a protected workflow, the editor’s primary action follows the review flow instead of deploying directly. On the configured environment branch, select Create branch to start editing. On a branch with uncommitted changes, select Review changes and commit the reviewed revision.

After committing the branch:

  1. Select Create pull request beside Run. Once a PR exists, this action becomes View pull request.
  2. Review the generated pull request in GitHub.
  3. Wait for the SteelEngine validation Check to finish.
  4. Follow the repository's normal approval and branch-protection policy.

The pull request targets the workspace’s Target branch from Settings > Source Control, for example develop or main, and summarizes the affected workflows and resource requirements. The editor names that target before branch creation and in the source-control bar. If other workflows on the branch have uncommitted changes, commit or discard those changes before opening the PR.

What Validation Checks

SteelEngine's test deployment validates the exact commit without modifying main or production. It checks:

  • Repository identity, commit reachability, and managed path boundaries
  • Bundle format, required files, references, and secret sanitization
  • Workflow graph structure, block types, operations, edges, and interfaces
  • Protected workflow dependencies and logical resource assignments
  • Deployment preflight for schedules, webhooks, APIs, and hosted surfaces

Validation parses extracted prompts and code but does not execute arbitrary workflow code. It also does not create triggers, change resource assignments, or create a deployment version.

Review the GitHub Check result and the Recent sync, apply, and publish jobs table under Settings > Source Control. Fix failures on the branch, commit again, and let the pull request revalidate.

Update a Branch from the Environment

The source-control bar identifies the configured target branch when that branch has advanced.

  1. Commit or discard all local branch changes.
  2. Select Update branch to merge changes from the configured target.
  3. If the update is clean, SteelEngine creates a normal merge commit on the branch.
  4. If conflicts appear, select Resolve.

SteelEngine uses a structured three-way merge instead of treating the workflow as an opaque JSON file. For each conflict, choose exactly one resolution:

ChoiceMeaning
oursKeep the value from your source-control branch
theirsKeep the value from the current environment branch
baseRestore the common ancestor's value
deleteRemove the conflicted item
Edit JSONProvide a valid custom JSON value

Select Resolve and update after every conflict has a valid resolution. SteelEngine validates the combined workflow and creates a two-parent merge commit. It never force-pushes the branch.

Merge the Pull Request

When the pull request is approved and its Check passes, merge it using the repository's normal merge policy.

The GitHub webhook queues an atomic environment-branch apply. SteelEngine validates the final commit tree, updates all affected protected main drafts together, and records the applied commit SHA. If any affected workflow fails validation, none of the main drafts move forward.

The merge still does not change the active deployment. Confirm the workflow shows Protected develop · read-only (using your configured branch name) and that Settings > Source Control shows the expected Applied commit before deploying.

If the webhook is delayed or missed, use Sync now in Settings > Source Control. It reports one result: the commit it synced to, Already up to date, the problem it hit, or, after about a minute, No result yet. Sync also repairs a missing hourly schedule and tells you if the repair failed. Scheduled reconciliation also repairs missed delivery without polling GitHub continuously. SteelEngine reconciles each active workspace binding about once an hour, with up to five minutes of jitter. If a run is missed while the worker is unavailable, SteelEngine catches it up within 15 minutes. After that, the next hourly run covers it.

Reconciliation skips removed connections and deleted workspaces before contacting GitHub or queuing another apply job. The workflow-level apply described here preserves the active runtime. A receiving workspace package follows its own manual or automatic deployment policy after a validated sync.

Understand Release Status

Open Source Control > Releases for the workspace-wide approval and live-version comparison. A summary line counts workflows that are live, need deploy, are pending, or have sync failures. Each workflow row shows its approved commit, its live version and commit, a state badge (for example Live, Approved, not deployed, Awaiting sync, or Sync failed), and one action: Open to deploy, Fix in editor, Review PR, or Open workflow. Previous versions under a row lists its retained Git-backed deployment versions; the tab covers the 100 most recent, and older versions stay in each workflow's deployment history. These are individual workflow releases, not an atomic release of the entire environment. See the workspace guide.

The workflow's source-control bar shows the environment and PR target, then distinguishes uncommitted edits, an open PR, a merged PR awaiting synchronization, and the approved synchronized commit. Synchronization errors appear as a separate state with recovery guidance.

The Live line reports the active deployment version and its source commit independently. The approved version is deployed appears only when both the source-control object and commit match the live version. Otherwise the UI identifies approved changes that still need deployment. A merged PR never claims that its workflow is live; return to the environment branch to confirm synchronization first.

Deploy Protected Main

  1. Open the protected workflow on its configured environment branch.
  2. Confirm there is no synchronization error.
  3. Resolve every required resource assignment.
  4. Select Deploy approved in the source-control bar. This separate action is available to admins only on the synchronized environment branch; editing branches use the pull-request flow.
  5. For an existing deployment, review and select Update in the deployment panel. For a first deployment, Deploy approved runs preflight and deploys the synchronized version.

The immutable deployment version records the Git commit SHA and branch provenance. Production triggers execute that deployment snapshot and do not need GitHub to remain available.

Roll Back

Use the workflow's deployment history to promote a previous deployment version back to live. The previous version retains its original source commit provenance.

For a receiving workspace connected to a Git package, use Workspace release history to prepare a reviewed rollback PR with a required reason. Completed workspace rollbacks show the restored release and reason in that history, including reverts created in Git. The workflow-level deployment history described here has a different scope.

Workflow-level rollback changes the active runtime version only. It does not rewrite Git, revert the configured environment branch, or change the protected main draft. If you also need to reverse main, merge a normal revert or repair pull request and synchronize it separately.

Effect of Each Action

ActionBranch working copyGitHubProtected mainActive runtime
Edit a branchChangesNo changeNo changeNo change
CommitBecomes cleanBranch advancesNo changeNo change
Open or validate a PRNo changeCheck updatesNo changeNo change
MergeNo changeEnvironment branch advancesSynchronizes after validationNo change
DeployNo changeNo changeNo changeNew immutable version becomes active
Roll backNo changeNo changeNo changeA previous immutable version becomes active

This separation makes the repository the review authority, protected main the approved SteelEngine draft, and the active deployment the production authority.

On this page