# .bricksignore Before publishing a package to the Bluebricks repository, it's suggested that large files that don't directly support the package's functionality be excluded. In addition, bricks CLI will automatically exclude runtime files and directories such as .terraform to ensure lightweight blueprints, easing the automation workflow. ## `.bricksignore` The bricks CLI uses `.bricksignore` file, that specifies intentionally untracked files to ignore. The file should be located in the root folder of a blueprint, next to [bricks.json](broken://pages/WT8nZ8bvssk2A9FFnomC). The file content is similar to the `.gitignore` pattern format, which is detailed in the [gitignore documentation article on the Git docs website](https://git-scm.com/docs/gitignore/en). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bluebricks.co/docs/orchestration/packages/artifacts-overview/.bricksignore.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.