Skip to content

Conversation

@mattjoyce
Copy link
Contributor

@mattjoyce mattjoyce commented Jan 30, 2026

Summary

  • Updates the .gooseignore documentation to accurately describe the auto-creation behavior introduced in PR Create default gooseignore file when missing #6498
  • Replaces the outdated "Default Patterns" section with detailed explanation of the auto-created file
  • Shows the exact content users will see in the auto-generated file
  • Adds tip about adding .gooseignore to .gitignore for projects that don't want it tracked

Test plan

  • Review rendered documentation for clarity
  • Verify code block matches actual auto-created content

@mattjoyce mattjoyce requested a review from a team as a code owner January 30, 2026 07:29
Update documentation to accurately describe how goose now auto-creates
a local .gooseignore file with default patterns when one doesn't exist.
This makes the ignore rules visible and easy to customize rather than
being hidden hardcoded defaults.

- Updated "Local ignore file" description to mention auto-creation
- Replaced "Default Patterns" section with "Auto-Created Local .gooseignore"
- Added the exact content of the auto-created file
- Added tip about adding .gooseignore to .gitignore if desired

Signed-off-by: matt joyce <[email protected]>
@mattjoyce mattjoyce force-pushed the docs/gooseignore-auto-creation branch from ca8386c to f77c055 Compare January 30, 2026 07:30
@dianed-square
Copy link
Contributor

Hi @mattjoyce Does #6802 change this behavior?

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