Monitoring and Managing Repositories
Learn how to view, classify, and manage repositories within connected change management systems in Sprinto.
Once your code repositories and ticketing systems are connected under Change Management Systems, Sprinto automatically begins monitoring them for compliance-related checks — such as peer reviews, branch protection, and code classification.
Each connected system (for example, GitHub, GitLab, or Azure DevOps) includes multiple tabs that let you view repository activity, integration branches, and peer review status. From here, you can view failing checks, classify repositories, assign owners, upload evidence, and manage compliance status across your codebase.
Accessing the Repository Dashboard
Navigate to Change Management Systems
Log in to the Sprinto dashboard.
Go to Data Library → Change Management.
On the Change Management Systems tab, click the connected provider (for example, Azure DevOps or GitHubApp).
View Provider Summary
The provider overview shows pending tasks and overall compliance status.
Example: 4 pending tasks (3 failing, 1 passing).
Tabs in the Repository Dashboard
Each connected provider includes four tabs that provide detailed insights:
Summary
Displays pending tasks, number of failing checks, and overall compliance health.
Repos Monitored
Lists all repositories being tracked, along with their classification, owner, and check status.
Integration Branches
Shows monitored branches and their associated checks (for example, merging or peer review rules).
Peer Reviews
Displays repositories where peer review requirements are being enforced or need attention.
Viewing and Fixing Checks
In the Repos Monitored tab, each repository displays:
Repo name
Account
Repo owner
Classification (Production or Not Production)
Current check status (Passing or Failing)
Click on any repository or failing check to open the Check Details drawer.
Review the issue under Check Details (for example, “Code repo should be classified”).
Use the three-dot menu to perform actions such as:
Upload evidence for unresolved checks.
Mark as special case for justified exceptions.
Manage assignment or escalation (for example, reassign to another owner).
Report issue if the check result appears inaccurate.
Classifying Repositories
In the Repos Monitored tab, click on a repository that is Unclassified.
Select Production Repo or Not Production Repo.
If choosing Production, select a CI branch to monitor.
Click Save to confirm.
Sprinto uses this classification to determine the compliance checks applied to that repository.
Assigning or Updating Repo Owners
Open a repository and select the Change option next to the repo owner field.
From the list of available users, select the new owner.
Click Update to confirm.
All existing and future checks for the repository will now be assigned to the new owner.
Managing Branch-Level Checks
Navigate to the Integration Branches tab.
Click a branch (for example,
mainordevelop) to view its associated checks.
Review failing checks such as:
“Branch protection rules should be enforced for admins”
“Merging of code changes should require passing status checks”
“Peer review should be enforced for code changes”
To fix, follow the How to Fix steps shown in the drawer. You can also upload evidence or mark as a special case if applicable.
Managing Organisations Under a Provider
In the provider view, click Manage next to the provider name.
Review:
Organisations monitored for code changes.
Organisations not monitored for code changes.
Click Manage next to each organisation to start or stop tracking.
To stop tracking, click Stop Tracking in the organisation details pane.
Best Practices
Regularly review the Summary tab to identify failing checks early.
Ensure all repositories are classified and assigned to an owner.
Use evidence uploads to maintain audit readiness for change-related controls.
Stop tracking inactive or deprecated repositories to avoid unnecessary alerts.
Last updated