Content Settings
The Content Settings tab holds organization-wide rules for how your content changes are reviewed and merged. The rules apply to every pipeline tree in the organization.
To reach it, click the hamburger menu on the top left, select
Merge Requirements
Require Unit Tests to Pass Before Merging
When this is enabled, a pipeline commit can only be merged once every unit test in its pipeline tree has last passed.
| State | Effect on merging |
|---|---|
| Commits merge without regard to test results. This is the default | |
| A commit whose tree has tests can only merge while all of them are passing |
Enabling it changes nothing for a pipeline tree that has no tests: the rule requires existing tests to pass, not that tests exist.
Only a pass clears a test. Failed, errored, and never run all block the merge — a test nobody has run establishes nothing about the change being merged.
The rule covers both ways of merging in the Pipeline Editor — the reviewed merge and merge-without-review — and it is enforced by the server, so it holds for any client, not only the web interface.
Toggle the setting and click
Permissions
Every member of the organization can read this tab — the same values drive the merge summary shown in the Pipeline Editor, so the rule is visible to the people it constrains.
Changing a setting requires CONTENT_SETTINGS_EDIT. Without it the toggle is disabled and explains why, and no save control is shown. See Roles.
If the current settings cannot be loaded, the tab reports the failure and offers a retry rather than showing the toggle. This is deliberate: a toggle rendered over a default rather than over the real value could otherwise be saved, silently turning the requirement off.