Documentation: Clarified negating VCS excluded files

[couling]

My earlier issue (#10418) was caused a misleading statement in the documentation which conflicts with a later statement:

Explicitly declaring entries in include will negate VCS' ignore settings.

As written, this is untrue because of the asymmetry between include and exclude:

If no format is specified, include defaults to only sdist.

In contrast, exclude defaults to both sdist and wheel.

So only declaring include entries with explicit formats can properly negate VCS.

To try to help future readers, I've moved the discussion of VCS down below the part on explicit formats so the closest code examples show explicit format, and clarified the note to inform readers the format must also be given.

Pull Request Check List

Resolves: #10418

• Added tests for changed code. (NA.)
• Updated documentation for changed code.

Summary by Sourcery

Documentation:

• Move the VCS ignore note below the explicit formats section and update its wording to specify that format must be provided when using include to override VCS ignore settings.

[sourcery-ai]

Reviewer's Guide

Refines the pyproject.toml documentation by removing a misleading note and repositioning the VCS ignore discussion to clarify that negating VCS ignore settings via include requires explicitly specifying the format.

File-Level Changes

Change	Details	Files
Removed misleading documentation about negating VCS ignore settings without explicit formats	Deleted the existing note block asserting include entries negate VCS ignore settings Removed the initial VCS seeding description under the exclude field	docs/pyproject.md
Repositioned and clarified VCS ignore note with explicit format requirement	Moved the VCS seeding discussion below the explicit formats section Added an updated note emphasizing that format must be set when using include to override VCS ignore	docs/pyproject.md

Possibly linked issues

• VCS exclude overrides cannot be overrden by "include" #10418: The PR clarifies documentation on how include interacts with VCS ignore settings, which likely caused the issue.
• VCS exclude overrides cannot be overrden by "include" #10418: The PR clarifies documentation to explain that include entries need explicit formats to override VCS excludes, resolving the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @couling - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Deploy preview for website ready!

✅ Preview
https://website-qrmhtszms-python-poetry.vercel.app

Built with commit c3461d8.
This pull request is being automatically deployed with vercel-action

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.