Change .merge
POST /{namespace}/changes/{change}/merge
Merge applies a Change to live data with a three-way, field-level merge against its base Version.
- Noun
- Change
- Mode
do- Event
Change.merged
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
change | Change | required | The reviewed Change. |
Outputs
| Output | Type | Required | Description |
|---|---|---|---|
version | Version | required | The new Version. |
change | Change | required | The Change, now merged into live data. |
Effects
- Emits
Change.merged. - Performed by the Engineering Lead.
- Sends the Change back to review when a field changed on both sides since its base.
- Never overwrites a concurrent edit.
Refuses when
| Check | Error | Fix | Then call |
|---|---|---|---|
| The key is valid, but its scopes do not allow this operation. | forbidden | Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them. | Change.merge |
| The record changed since it was read, so the write would overwrite a newer version. | conflict | Read the record again, then retry the write against its current state. | Change.merge |
| The record is not in a state that allows this Verb, so the call is refused. | refused | Read the record, run the Verb that moves it to an allowed state, then retry. | Change.merge |
When it waits
| Gate | Default |
|---|---|
| Decision class | Low: two-way, nothing at stake |
| Delay window | None: it runs once review passes. |
| Limit | The call Limit of the Permission it runs under. |
| Over the Limit | It waits pending for an Approval from the Founder. Approved, it runs; refused, it ends refused with limit-exceeded; unanswered by its deadline, it ends canceled. |