> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/commands/ignore-create.md). # Ignore create The snyk ignore create command that creates a Snyk Code ignore ## Usage and description `snyk ignore create --finding-id= --ignore-type= --reason= --expiration= [--org=] [--remote-repo-url=] [OPTIONS]` The `snyk ignore create` command creates an ignore for a Snyk Code finding using Consistent Ignores for Snyk Code. Snyk stores the ignore on the finding and applies it consistently across the CLI, IDE, and other integrations on the next test. **Note:** This command applies only to Snyk Code. To ignore Snyk Open Source or Snyk IaC issues, use the [`snyk ignore`](/developer-tools/snyk-cli/commands/ignore.md) command without the `create` subcommand. Creating ignores from the command line is an Early Access feature of the Ignore Approval Workflow. It applies to `snyk code test` runs from the CLI and IDE. It does not apply to SCM (stateful) tests run through the Import API, and it does not support CLI Upload projects. ## Prerequisites Complete the following before you create an ignore: * Install Snyk CLI v1.1297.1 or later. Visit [Install or update the Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli). * Enable Consistent Ignores for Snyk Code for your Group or Organization. Visit [Consistent Ignores for Snyk Code](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code). * Set the Organization that holds the ignores. Visit [How to select the Organization to use in the CLI](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli). * Commit and push your code to the remote repository so that reviewers can locate the finding. This command identifies a finding by its finding identifier. To obtain it, run `snyk code test --json` and locate `runs.results[n].fingerprints.snyk/assets/finding/v1` in the output. Visit [Consistent Ignores for Snyk Code CLI](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/snyk-cli#access-the-finding-identifier-in-json-and-sarif-output). ## Interactive and non-interactive modes By default, `snyk ignore create` runs interactively and prompts for each value. Run the command without options to use interactive mode. To run non-interactively, for example in a script or CI/CD pipeline, provide all required options. ## Options ### `--finding-id=` Finding to ignore. Required. Obtain the finding identifier from the JSON output of `snyk code test --json`. ### `--ignore-type=` Reason category for the ignore. Required. ### `--reason=` Human-readable justification for the ignore. Required and must not be empty. ### `--expiration=` Expiration date in `YYYY-MM-DD` format, or `never`. Required in non-interactive mode. ### `--org=` Organization that holds the ignore. The value must be a valid Organization ID. Default: the Organization set in your CLI configuration ### `--remote-repo-url=` Repository URL for the finding. Snyk detects this automatically when a .git directory is present. Specify it explicitly when the repository has a different Git URL. To verify the URL, run `git remote -v`. ## Examples for the `snyk ignore create` command ### Create an ignore interactively ``` $ snyk ignore create ``` ### Create an ignore non-interactively ``` $ snyk ignore create \ --finding-id= \ --ignore-type=wont-fix \ --reason="Not exploitable in this context" \ --expiration=2026-12-31 \ --org= ``` --- # 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.snyk.io/developer-tools/snyk-cli/commands/ignore-create.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.