This article explains how Novus uses pull requests (PRs) to manage your tracking configuration and review code changes. Using automated PR workflows allows you to keep your tracking up to date while maintaining full control over your codebase.

When Novus creates a PR

Novus generates a PR when it needs to apply code changes to your repository. You can expect Novus to create a PR in the following scenarios:

When Novus generates these changes, it creates a new branch and opens a PR targeting your default branch.

Human-approved PRs

Novus never merges code into your repository automatically. When Novus creates a PR, it requires human review and approval before any changes take effect.

You always retain full control over your codebase. You and your team can review the code, leave comments, make adjustments, and merge the PR using your standard development workflow. Novus tracks the status of the PR and updates your dashboard when the PR is closed or merged.

Additional PR functionality

Beyond creating PRs for code changes, Novus can monitor and analyze the PRs created by your development team. You can manage these automated workflows by going to Admin and updating your PR Settings.

You can view the status of all active and completed analyses by selecting PR Reviews from the left menu.