Skip to main content
Releasing adds a finished feature to your app’s code. Iron Octopus merges the feature into your project’s main branch, with a full record of what was asked for, built and checked.
Releasing doesn’t deploy your app. It adds the feature to your project’s code, ready for however you ship it.

​
When a feature is ready

A feature is ready to release when every required acceptance criterion is met. It then shows under Needs you on Home as Ready to release.

​
Release it

1

Check the acceptance criteria

Open the feature and read each acceptance criterion’s verdict and evidence. By default, criteria are checked by review; the page says when a test or a running environment wasn’t used.
2

Click Release feature

This records your approval of the release. Iron Octopus creates a pull request and merges the feature branch into your project’s main branch.
3

It's released

While the merge runs, the feature shows as Releasing. When it finishes, the feature is Released and its record is read-only.

​
If the release stops

If the merge can’t finish, the feature shows Releasing · needs attention. Open it to see why, then click Retry release. The feature stays in Acceptance until the release succeeds, so nothing is half-released.

​
After release

A released feature doesn’t change. If you find a problem with it later, report a defect. The fix is a new feature, and the original stays exactly as it was released.

​
Changing the rule

Approving the release is a built-in rule that’s on by default. You can change it so features release on their own once every acceptance criterion is met.