Documentation Docs version: dev (Pre-release: Gitoodo has not been released yet)

For users · Orchestrator

Merge control and release planning

On this page
  1. Merge control
  2. Release planning

The orchestrator merges a pull request once every check is green. Choose the merge style in Settings under Orchestration; the repository must allow it.

Merge control#

  • Hold: the pull request waits until you release it.
  • Veto: it is never merged automatically, and the issue waits for you.
  • Release lifts either one.

Auto-merge that is already switched on at the forge can only be stopped there.

Release planning#

Release planning uses the forge's milestones. An issue enters the next release with the release:next label, as a dependency of a release issue or with priority:p0.

The due date is a decision point: Gitoodo asks whether you release, move or extend. Nothing is ever cut automatically.

Whether a repository plans releases is set on its detail page.

The same text is in the app under Help & Feedback → Help center.

Docs version: dev