Fix broken gitignore exclude

[Luap99]

.gitignore: do not ignore all build directories

This matches all directories not just the top level one we wanted to
ignore, however we no loner use or put anything into /build so we can
just remove it instead.

vendor: regenerate files

Now that build is no longer incorrectly excluded it gets added. The fact
that this did not cause a compile failure was just because gingko is
used directly by the tests and not compiled from these sources.

Summary by Sourcery

Fix .gitignore to stop excluding build directories and regenerate vendor files accordingly

Bug Fixes:

• Remove the build directory exclusion from .gitignore to prevent unintended ignores

Chores:

• Regenerate vendor files to include the previously excluded build_command.go

[sourcery-ai]

Reviewer's Guide

This PR corrects an overly broad .gitignore rule by removing the top‐level “build” exclusion and regenerates vendor dependencies so the newly included files (previously ignored) are added.

File-Level Changes

Change	Details	Files
Remove incorrect build directory ignore	Delete top‐level /build rule from .gitignore	.gitignore
Regenerate vendor to include newly unignored build files	Add ginkgo build_command.go under vendor Refresh vendor directory contents	vendor/github.com/onsi/ginkgo/v2/ginkgo/build/build_command.go

---

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 @Luap99 - 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.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, sourcery-ai[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Luap99]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mheon]

Ouch - easy to forget how Gitignore semantics are not always a match for what we want to do.

LGTM

[mtrmac]

/lgtm