Run e2e tests on push to main instead of on every PR

[jsmid1]

The cli-e2e PipelineRun runs the conforma/e2e-tests pipeline which takes ~25 minutes per run. Moving it from pull_request to push trigger means e2e tests run post-merge on main.

Ref: https://issues.redhat.com/browse/EC-1930

[coderabbitai]

Warning

Review limit reached

@jsmid1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: d86091c5-4b35-4ce1-8003-fd2980cb4c4e

📥 Commits

Reviewing files that changed from the base of the PR and between 33b9c36 and ae7c2c2.

📒 Files selected for processing (1)

• .tekton/cli-e2e-push.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:11 AM UTC · Completed 8:14 AM UTC
Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

Review

Verdict: Approve ✅

Summary

This PR moves the e2e test PipelineRun trigger from pull_request to push on main, reducing CI time for PRs by ~25 minutes per run. The e2e tests will now run post-merge instead of on every PR.

Changes reviewed

Single file renamed: .tekton/cli-e2e-pull-request.yaml → .tekton/cli-e2e-push.yaml

Change	Rationale
Removed pull_request_number annotation	Not applicable for push events
cancel-in-progress: "true" → "false"	Each push to main is a distinct merged commit; canceling prior runs would skip validating those commits
CEL expression: event == "pull_request" → event == "push"	Core trigger change
name: cli-e2e-on-pull-request → cli-e2e-on-push	Consistent rename

Analysis

• Correctness: All four metadata changes are internally consistent. The spec section (params, pipelineRef, taskRunTemplate) is unchanged. The naming convention matches the existing cli-main-push.yaml. No dangling references to the old filename or PipelineRun name exist elsewhere in the repo.
• Security: No security implications. No changes to secrets, RBAC, or permissions.
• Scope: Tightly scoped — single file, single purpose, matching the stated intent and the referenced issue (EC-1930).
• Conventions: File and resource naming follows the established pattern (cli-main-push.yaml / cli-main-on-push).
• Documentation: No documentation updates needed for this CI configuration change.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	54.26% <ø> (+<0.01%)	⬆️
generative	16.80% <ø> (ø)
integration	27.97% <ø> (ø)
unit	71.74% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.