If you don’t want Firebender to analyze files without explicit permission, then add the file to the ignore array in firebender.json. This ignore allows for glob patterns similar to what you find in .gitignore.

​
Example: ignore all secrets.properties files

In $projectRoot/firebender.json:

firebender.json
{
  "ignore": [
    "**/secrets.properties"
  ]
}

Warning: Firebender will only respect the ignore list for implicitly added context.

  • If you manually copy code snippets from a file that is in ignore and paste it into chat, Firebender will assume that you want to include it in the context.
  • If you explicitly run an inline AI change in an ignore file, Firebender will still use that file in context because you explicitly requested a change.
  • Autocomplete will never use files or work on files that are in ignore because it is considered an implicit behavior.

Best practice is to never have production api keys stored in your local development environment.

If you don’t want Firebender to analyze files without explicit permission, then add the file to the ignore array in firebender.json. This ignore allows for glob patterns similar to what you find in .gitignore.

​
Example: ignore all secrets.properties files

In $projectRoot/firebender.json:

firebender.json
{
  "ignore": [
    "**/secrets.properties"
  ]
}

Warning: Firebender will only respect the ignore list for implicitly added context.

  • If you manually copy code snippets from a file that is in ignore and paste it into chat, Firebender will assume that you want to include it in the context.
  • If you explicitly run an inline AI change in an ignore file, Firebender will still use that file in context because you explicitly requested a change.
  • Autocomplete will never use files or work on files that are in ignore because it is considered an implicit behavior.

Best practice is to never have production api keys stored in your local development environment.