> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/whats-new/september-2026/bulk-upload-code-scope-rules.md).
# Bulk Upload Code Scope Rules
Managing code scope rules across dozens of applications just got dramatically faster. You can now upload, validate, and apply rules for all your apps in a single CSV workflow, instead of configuring them one application at a time.
### What's New
* **Bulk CSV upload** for code scope rules across all applications in your SeaLights account, replacing the previous per-app, per-rule interface.
* **Two upload modes**: choose to **Append** new rules on top of existing ones, or **Replace All** rules with the contents of your CSV file.
* **Instant validation** on upload, column structure and every row value are checked immediately, with clear error and warning indicators so you can fix issues before applying.
* **Method-level rules** are now supported in the CSV format, allowing you to exclude or scope specific methods (not just file paths) directly from your bulk upload.
### Why It Matters
Code scope rules control what SeaLights measures - which files and methods count toward coverage, which are excluded, and which test stages each rule applies to. For teams managing many applications, maintaining these rules individually is time-consuming and error-prone.
Bulk upload makes it practical to treat code scope configuration as a managed artifact: version-controlled, reviewable, and deployable in bulk. A change that previously required dozens of manual UI interactions can now be done in minutes - export, edit, validate, apply.
### Get Started
* [Code Scope (Ignore/Include) - Documentation](https://docs.sealights.io/knowledgebase/settings/code-scope-ignore-include)
* Navigate to **Settings → Code Scope (Ignore / Include)** and click **Bulk Upload Rules**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sealights.io/knowledgebase/whats-new/september-2026/bulk-upload-code-scope-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
