Skip to content

Conversation

@MichaReiser
Copy link
Member

@MichaReiser MichaReiser commented Jun 13, 2025

Summary

Document the new src.include and src.exclude fields (not yet released)

Note: The include field is currently missing in the generated docs. It will exist once my overrides PR is merged (it's when I noticed that it's missing). This is hopefully before the next release.

@MichaReiser MichaReiser added the documentation Improvements or additions to documentation label Jun 13, 2025
@MichaReiser MichaReiser force-pushed the micha/include-excluede branch from a07b121 to 832029a Compare June 13, 2025 13:26
@MichaReiser MichaReiser marked this pull request as ready for review June 13, 2025 13:34
Copy link
Contributor

@sharkdp sharkdp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

docs/README.md Outdated

Both `include` and `exclude` support gitignore like glob patterns:

- `src/` matches only a directory
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this maybe describe whether or not the directory contents would be affected?

docs/README.md Outdated
- `src` matches files or directories named `src`
- `*` matches any (possibly empty) sequence of characters (except `/`).
- `**` matches zero or more path components.
This sequence **must** form a single path component, so both `**a` and `b**` are invalid and will result in an error.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm very confused by this examples (**a, b**), is there some kind of context that's required here? Would it be useful to include a directory tree as an example where this example is relevant?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think a directory tree would help here. These patterns are not valid syntax. ** can only be used like /**/a but not inside a path component

@MichaReiser MichaReiser force-pushed the micha/include-excluede branch from 2fe1c05 to a500a6f Compare June 18, 2025 08:54
@MichaReiser MichaReiser enabled auto-merge (squash) June 18, 2025 09:10
@MichaReiser MichaReiser merged commit 5f2a43e into main Jun 18, 2025
10 checks passed
@MichaReiser MichaReiser deleted the micha/include-excluede branch June 18, 2025 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants