Configuring and Using Settings Presets for PR Integration

CodeScene's Settings Presets feature allows you to define reusable configurations for your projects. This is especially useful when managing pull request (PR) integration across multiple repositories, as it ensures consistency and reduces repetitive setup work.


What Are Settings Presets?

Settings presets are templates that store configuration options that can be reused across multiple projects. In the context of PR integration, they streamline how GitHub App, Bitbucket, GitLab, or Azure DevOps integrations are set up.

  • Active Presets appear in dropdowns when configuring a project.

  • Deactivated Presets won’t show up in project configuration pickers.

  • Presets in Use cannot be deleted—remove their usage from all projects first.


How to Create a Settings Preset for PR Integration

  1. Navigate to Configuration → Settings Presets.

  2. Select a preset type (e.g., PR Check – GitHub App) from the list.

  3. Click on New.

    You'll be prompted to enter the required information for the integration.  

  4. Click Save once the preset is configured.


Entering the required information for the integration

GitHub App:

GitLab:

Azure DevOps

Bitbucket

Bitbucket Server

Gerrit


Apply the Preset to a Project

Now that your preset is created:

  1. Go to your Project Configuration.

  2. Navigate to the PR Integration section.

  3. Enable the PR Integration and select the relevant platform (e.g., GitHub App).

  4. Use the dropdown to select your newly created preset.

  5. Click Save Configuration.

Your project is now set up to use the selected preset for PR integration.


Managing Presets

  • To deactivate a preset, simply click on the Deactivate button in the Settings Presets view. It won’t be removed, but it will no longer appear in selection menus.

  • To delete a preset, ensure it's not in use by any project.


Benefits of Using Settings Presets

  • Time-saving: Configure once, reuse everywhere.

  • Consistency: Avoid human error across multiple project configurations.

  • Central management: Easy to update or retire credentials.