Inconsistent glob pattern resolution in nested monorepo configurations

When utilizing a monorepo structure with nested biome.json files, the ignore property occasionally fails to resolve paths consistently across different environments. While local development respects the root-level ignores, production CI/CD pipelines often process files that should be excluded based on nested glob patterns.

The discrepancy arises when complex glob patterns are defined relative to the project root but executed from a subdirectory that contains its own configuration. It is unclear if the Biome engine merges these patterns hierarchically or if the nearest configuration file takes absolute precedence, potentially leaving un-linted or improperly formatted files in production builds.

How does Biome resolve conflicting ignore patterns when multiple configuration files exist in a directory tree? Is there a documented mechanism to ensure global ignore patterns are strictly enforced across all sub-package boundaries?