Skip to main content
Early accessBeta, invite only since 1 Nov 2026. A person reads every application.Apply for an invite
Demystify OS

Workflow in Demystify Skills Hub

Change to release

From a requested change to a released one, checked by a second reviewer, released by the owner.

Apply for the betaAll entries
Provisioned on requestR3 A person does the last step. On request, as of 4 Nov 2026.

From a requested change to a released one, checked by a second reviewer, released by the owner. This workflow is in the Engineering category at risk tier R3, a person does the last step. A person is designed to decide at step 5. It is on request as of 4 Nov 2026, with no measured run yet.

How it works

The steps

  1. 1

    Write the acceptance criteria for the change.

  2. 2

    Build the change in its own branch.

  3. 3

    A second reviewer checks it.

  4. 4

    Open the pull request with the evidence.

  5. 5

    The owner releases it.Designed: a person decides here.

Detail

What it needs and where it stops

What it needs from you
  • Change request
What it needs connected
  • Code host
Risk tier R3: A person does the last step
Money, deletion or filing: designed so that a person does the final step. 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.
Status and what is not claimed
It is on request as of 4 Nov 2026: a catalogue entry we set up with you. No run of it has been measured yet, and nothing here claims it installs, syncs or streams on its own today.

Want this set up?

Apply for the invite-only beta. A person reads every application.

Apply for the beta