Skip to content

Conversation

@mattjoyce
Copy link

@mattjoyce mattjoyce commented Jan 14, 2026

Summary

  • automatically create .gooseignore the first time we need the built-in safety patterns so the defaults are visible/
    editable instead of hidden in code
  • share those defaults through a single constant and cover them with an explicit test

Testing

  • cargo fmt
  • cargo test -p goose-mcp test_default_patterns_when_no_ignore_files

@mattjoyce mattjoyce force-pushed the gooseignore-visible-defaults branch 2 times, most recently from 6cff713 to 26e68ed Compare January 14, 2026 12:06
@blackgirlbytes
Copy link
Contributor

love that the default is there to keep average users from messing up their secrets files, but if theyre more advanced..they have the option to edit the ignore file.

@mattjoyce mattjoyce force-pushed the gooseignore-visible-defaults branch from 26e68ed to e451223 Compare January 14, 2026 21:45
@mattjoyce
Copy link
Author

Thinking about it, we can help user more. I have added some guidance into the default .gooseignore, including some other examples of files that users might unintentionally expose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants