Skip to content

Conversation

@gauron99
Copy link
Contributor

@gauron99 gauron99 commented Nov 1, 2025

Seeing the annoyance of the verify check in PRs because of this merge of our custom components auto bump and the general knative-wide auto deps bump Im separating these (again).

We have to manually approve (and reopen to run tests) these PRs but it turn it doesn't block any "real PRs" that come in at unfortunate time when some components get bumped.

@knative-prow knative-prow bot requested review from jrangelramos and nainaz November 1, 2025 12:29
@knative-prow knative-prow bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 1, 2025
@codecov
Copy link

codecov bot commented Nov 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.14%. Comparing base (b2b8009) to head (398e64d).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3165      +/-   ##
==========================================
+ Coverage   59.39%   60.14%   +0.75%     
==========================================
  Files         134      134              
  Lines       13500    13500              
==========================================
+ Hits         8018     8120     +102     
+ Misses       4539     4408     -131     
- Partials      943      972      +29     
Flag Coverage Δ
e2e-tests 41.68% <ø> (+1.46%) ⬆️
integration-tests 54.67% <ø> (+1.65%) ⬆️
unit-tests 46.71% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gauron99 gauron99 requested review from lkingland and matejvasek and removed request for jrangelramos and nainaz November 3, 2025 10:41
@gauron99
Copy link
Contributor Author

gauron99 commented Nov 7, 2025

/hold might have a better fix

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 7, 2025
Copy link
Member

@lkingland lkingland left a comment

Choose a reason for hiding this comment

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

/lgtm
Nice enhancement!

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 11, 2025
@knative-prow
Copy link

knative-prow bot commented Nov 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gauron99, lkingland

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants