Skip to content

ci: skip export provenance on pull requests from forks - #66

Merged
oll4com merged 1 commit into
mainfrom
ci/skip-provenance-on-fork-prs
Oct 29, 2026
Merged

oll4com merged 1 commit into
mainfrom
ci/skip-provenance-on-fork-prs

Conversation

@oll4com

@oll4com oll4com commented Oct 16, 2026

Copy link
Copy Markdown
Owner

Every pull request from a fork failed CI at "Verify export provenance": a contributor's change makes the exported files differ from PUBLIC_EXPORT_MANIFEST.json by design. The step now runs on pushes to main and on same-repository branches only.

Checked locally: a contributor change fails verify-export-provenance.mjs and still passes public-export.mjs, the next CI step.

Merge note: the public repo is published from the release overlay. Carry this commit into the overlay at the next release, or merge here and fast-forward the overlay before the next sync.

Outside contributors change exported files, so the manifest check always
failed their pull requests (bounty issues #60-#65). Pushes to main and
same-repository branches are still verified.
@coderabbitai

coderabbitai Bot commented Oct 16, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1440af28-dc34-48cb-b64d-f0ede0ad8867
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

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

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.

1 participant