Project113

Repository Settings

Repository settings let you configure how the platform handles merging, branching, CI/CD, and more.

Accessing Settings

Navigate to your repository and click the Settings tab in the sub-navigation bar.

Merge Strategy

Choose the default merge strategy for change requests in this repository:

  • Merge — Creates a merge commit that combines all changes from the source branch.
  • Squash — Squashes all commits from the source branch into a single commit on the target.
  • Rebase — Replays individual commits from the source branch on top of the target.

This default can be overridden per change request or by CR policies.

Sync Strategy

Choose how change requests stay up to date with the target branch when it advances:

  • Manual — The author manually updates the source branch.
  • Merge — Automatically merges the target branch into the source branch.
  • Rebase — Automatically rebases the source branch onto the target.

Branch Naming

Configure the default branch name created when initializing a repository (typically master).

CI/CD Configuration

Set the default location and behavior for CI/CD pipelines:

  • Config files — The file or directory the platform reads for pipeline configuration (default: .project113/).
  • Data retention — How many days to keep CI/CD job metadata (default: 60).
  • Log retention — How many days to keep CI/CD job logs (default: 30).

See the CI/CD Configuration guide for details on config file formats.

Change Request Defaults

Configure default requirements for change requests:

  • Require CI to pass — Block merging until CI pipelines succeed.
  • Minimum approvals — Require a minimum number of approving reviews.
  • Require all threads resolved — Block merging until all discussion threads are resolved.
  • Allow force merge — Permit merging even when requirements are not met.
  • Auto-delete source branch — Remove the source branch after merging.

Auto-merge — Automatically merge a change request once it meets all of its requirements (approvals, CI, resolved threads, merged dependencies). See Auto-Merge for how it works.

Auto-retarget — Automatically retarget dependent change requests when the target branch of a CR changes, so they follow their dependency after it merges. See Dependencies.

Change Request Formatting

  • Use CR title as commit message — Use the change request title as the default merge commit message.
  • Custom commit message — Set a default commit message template for merges.
  • Use random CR IDs — Generate random change request identifiers instead of sequential numbers.

CR ID Format

Choose how change requests are identified: by sequential number (e.g., #42) or by random ID.

See the Permissions Reference for a complete list of all repository permissions, their keys, and what they control.