-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Global .gooseignore negation pattern not working #6155
Copy link
Copy link
Labels
Description
Description
When trying to access a .env.example file in a project, Goose blocks access with the error:
Access to '/path/to/project/.env.example' is restricted by .gooseignore
Environment
- Local .gooseignore: Does not exist in the project directory
- Global .gooseignore at
~/.config/goose/.gooseignorecontains:!.env.example
Expected Behavior
The ! prefix should negate the pattern and explicitly allow access to .env.example files, following the standard gitignore-style negation syntax.
Actual Behavior
Goose still blocks access to .env.example files despite the negation pattern in the global .gooseignore.
Possible Causes
- The negation pattern (
!) isn't being parsed correctly - There's a default internal rule blocking
.env*files that the negation isn't overriding - The global
.gooseignorefile isn't being read/applied properly
Steps to Reproduce
- Create a global
.gooseignoreat~/.config/goose/.gooseignorewith content!.env.example - Ensure no local
.gooseignoreexists in the project - Try to view or edit a
.env.examplefile using Goose - Observe the access restriction error
Reactions are currently unavailable