Skip to content

fix(CI): Fork friendly CI jobs - #534

Open
cnihelton wants to merge 3 commits into
mainfrom
fork-friendly-ci
Open

cnihelton wants to merge 3 commits into
mainfrom
fork-friendly-ci

Conversation

@cnihelton

Copy link
Copy Markdown
Collaborator

This PR aligns the criteria with which both e2e.yaml and build-pr.yaml jobs run. The latter is a slightly lighter job, thus it makes more sense to run it even when PRs are in draft while the other is heavier, thus it should only run when flagged as ready.
Most importantly, this PR makes PRs coming from forks no longer need to interact with signing certificates. For build-pr.yaml it means skipping the package signing part. For e2e.yaml it means always provisioning a fresh cert - for all PRs, not only forks.

@cnihelton
cnihelton marked this pull request as ready for review October 26, 2026 19:11
@cnihelton
cnihelton requested a review from a team as a code owner October 26, 2026 19:11
This avoids issues with PRs coming from forks with legitimate code
changes that demand running the end-to-end tests.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

No unresolved issues were identified in the reviewed workflow changes.

No open issues 🎉

What changed in this PR

Updates CI workflows to support forked pull requests while aligning draft-build and E2E execution criteria.

Changes:

  • Runs lightweight builds for draft pull requests while limiting E2E jobs to ready pull requests.
  • Skips signing requirements for forked builds.
  • Provisions a temporary self-signed certificate for E2E package installation.
File Description
.github/​workflows/​e2e.yaml Updates triggers, skips draft runs, and provisions a temporary trusted certificate.
.github/​workflows/​build-pr.yaml Enables draft builds and conditionally skips certificate installation and package signing for forked pull requests.

Review effort: Lite

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants