CodeScene Access vs. CodeScene Delta Analysis: which GitHub App do you need?

Overview

If you connect CodeScene to GitHub, you may have run into two different GitHub Apps with similar names: CodeScene Access and CodeScene Delta Analysis. Delta Analysis was CodeScene's original GitHub App. CodeScene Access replaced this and is now the only app you need.

This article explains what each app does, why you might see a "not installed" warning even when your integration is working, and how to move from Delta Analysis to CodeScene Access.

The short answer

You only need CodeScene Access installed. It fully replaces CodeScene Delta Analysis, there's no CodeScene feature today that still depends on the old app. If you're currently running both, you can safely remove Delta Analysis once CodeScene Access is installed and configured for your repositories.

What each app does

CodeScene Access (current) The single GitHub App CodeScene needs today. It handles authentication and repository-level access for pull request analysis, checks, and code coverage gates. Access is granted per repository, so you decide exactly which repositories CodeScene can see.

CodeScene Delta Analysis (legacy) CodeScene's original GitHub App. It has been fully superseded by CodeScene Access and is no longer required for any CodeScene feature, including pull request checks and code coverage.

Why you might see a "not installed" warning

CodeScene's Pull Request Integration page checks specifically for CodeScene Access's access to each repository, not Delta Analysis. If a repository only has Delta Analysis installed, even if that installation covers "all repositories" in your GitHub organization, you'll see a warning like:

The GitHub App CodeScene Access is not installed for some of your repositories. You need to install it first.

This is expected, and it's intentional: the warning is designed to prompt customers still on the legacy app to move to CodeScene Access. It will keep showing up for a repository until CodeScene Access itself is installed and granted access to it, regardless of whether Delta Analysis is installed and otherwise working fine.

Note: A separate error, "Couldn't find check to update," can appear during code coverage analysis. This is unrelated to which GitHub App is installed and has a different cause. If you're seeing this error, refer to other articles on this subject rather than following the steps below.

Moving from Delta Analysis to CodeScene Access

  1. In GitHub, go to Settings, then use Switch settings context (top right) to select your organization.

  2. On the left, select GitHub Apps, then Configure next to CodeScene Access.

  3. Under Repository access, choose All repositories, or select Only select repositories and add the repositories you use with CodeScene.

  4. Click Save. The page shouldn't reload if the save succeeded. If it keeps reloading without the repository showing as saved, try again or refresh the page before continuing.

  5. Back in CodeScene, open the project's Pull Request Integration settings and confirm the warning has cleared for that repository.

  6. Once CodeScene Access is confirmed working for all your repositories, you can uninstall CodeScene Delta Analysis: in GitHub, go to Settings → GitHub Apps, select CodeScene Delta Analysis, and uninstall it. This step is optional, but recommended as it reduces the number of apps with access to your source code to just the one you actually use.

Key takeaways

  • CodeScene Access is the only GitHub App CodeScene needs today.

  • Delta Analysis has been fully superseded and is not required for analysis, PR checks, or code coverage.

  • The "not installed" warning appears whenever CodeScene Access itself lacks repository access, even if Delta Analysis is installed and working. It's a deliberate nudge to migrate, not a bug.

  • Once CodeScene Access is installed and confirmed working, Delta Analysis can be safely uninstalled.

  • "Couldn't find check to update" is a separate, unrelated issue, don't confuse it with this warning.