Incident write-up

1. Write the acceptance criteria for the change.
2. Build the change in its own branch.
3. A second reviewer checks it.
4. Open the pull request with the evidence.
5. The owner releases it.

Needs from you: Change request.

What it needs connected: Code host.

Where a person is designed to decide: The owner releases it.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the change and its description.
2. Write criteria that can be checked.
3. List the manual steps and the evidence for each.
4. A person confirms the plan.

Needs from you: Change description.

Where a person is designed to decide: A person confirms the plan.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the dependency list.
2. Check each for newer versions.
3. Write the list with the riskiest first.

Needs from you: Dependency list.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.