• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In
Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
New Repo Setting:
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?

Enabling this setting will include a (potentially inaccurate) coverage % with warning messages in status updates for drifted builds.

Adjust setting

kubernetes-sigs / kubebuilder / 39140719758
88%
master: 89%

Build:
Build:
LAST BUILD BRANCH: fix/6186-typos
DEFAULT BRANCH: master
Ran 15 Nov 2026 12:02PM UTC
Jobs 1
Files 103
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Oct 2026 03:28PM UTC coverage: 87.534%. Remained the same
39140719758

Pull #6086

github

Yan123-tech
Add an integration spec covering the webhook update path

`kubebuilder create webhook` can extend a webhook that already exists for
a kind, going through WebhookUpdater instead of the fresh-file template.
The current specs only grep the generated files, and every CLI call uses
--make=false, so nothing builds a project whose webhook was extended
later and nothing checks that the extended webhook is actually served.

The new spec, next to "should preserve customizations when adding new
webhook types":

- creates two kinds and extends each webhook in two steps, one in each
  order (--defaulting then --programmatic-validation, and the reverse);
- after each step fills in the generated handler, and before extending
  adds a function of its own, the way a user does;
- checks the user's function survived the second create webhook;
- adds a small test per kind to the throwaway project's webhook package
  and runs the project's `make test`, which builds the project and runs
  the webhook suites under envtest: one object with the field unset is
  expected to be defaulted, and one with a disallowed value is expected
  to be rejected with the user's error.

The added test file only ever exists inside the throwaway project the
spec generates; no template changes and no new file reaches CLI users.

Signed-off-by: Yan123-tech <180288779+Yan123-tech@users.noreply.github.com>
Pull Request #6086: Add an integration spec covering the webhook update path

9023 of 10308 relevant lines covered (87.53%)

442.99 hits per line

Jobs
ID Job ID Ran Files Coverage
1 39140719758.1 15 Nov 2026 12:02PM UTC 103
87.53
GitHub Action Run
Source Files on build 39140719758
  • Tree
  • List 103
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #6086
  • PR Base - master (#39038575120)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc