Cocov
Docs GitHub
Introduction
Installation, Administration & Maintenance
Infrastructure
Platform Components
API
Configuration Options
Sidekiq Web UI
Worker
Configuration Options
Cache
Configuration Options
Badger
Installation
Requirements Creating a GitHub App
Installing on Kubernetes using Helm
Choosing a Storage Medium Initializing the API and Web UI Initializing the Worker instance Enabling the Badger Enabling Worker Cache
Starting an Instance Using Docker Compose
Administration
Users Permissions Service Tokens Repositories Personal Access Tokens Badges Organization & Repository Settings Sidekiq Dashboard Caches
Configuring a Repository to Use Cocov
Checks & Limits: The Manifest File Uploading Test Coverage to Cocov Protecting the Manifest File Blocking PRs using Cocov Results Supported Coverage Formats
Plugin Development
What is a Cocov Plugin Cocov SDKs Testing Plugins Locally with PlugDev Distributing Your Plugin
Troubleshooting

Protecting the Manifest File

Last updated Feb 26, 2024

As noted in other pages, the manifest file includes all configurations required to run Cocov in a repository, and also how it should behave. Preventing unauthorised access is essential in order to maintain consistency.

In order to do that, repository administrators and maintainers may configure pull requests to enforce reviews from specific people and groups when specific files are changed. To use this feature, refer to the CODEOWNERS documentation on GitHub.

However, setting a CODEOWNERS file is not enough. After you are done and CODEOWNERS is already on your default branch, refer to Protected Branches documentation.