Skip to content

ci: e2e check for #1311, fork PR touching a release step (do not merge) - #1314

Closed
romchornyi wants to merge 1 commit into
dashpay:ci/harden-workflowsfrom
romchornyi:ci/e2e-fork-release-step
Closed

romchornyi wants to merge 1 commit into
dashpay:ci/harden-workflowsfrom
romchornyi:ci/e2e-fork-release-step

Conversation

@romchornyi

Copy link
Copy Markdown
Contributor

Throwaway draft PR from a fork for the GitHub checks of #1311. Do not merge; it will be closed.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 4, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • 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

@thepastaclaw

Copy link
Copy Markdown
Contributor

🕓 Review not started yet because this PR is a draft.

  • Request normal review — click when the PR is ready for review.
  • Request priority review — click to move this review to the front of the queue.

Commit bd500ca. Normal review starts when eligible; priority review starts as soon as a slot is available.

@romchornyi

Copy link
Copy Markdown
Contributor Author

Done: workflow-lint passed on a fork PR without secrets and put the workflow_policy.release_only_step_changed warning on the changed line (release-dashpay-testflight.yml:333, run 41862658260). Results are in #1311.

@romchornyi romchornyi closed this Nov 4, 2026
@romchornyi
romchornyi deleted the ci/e2e-fork-release-step branch November 4, 2026 17:54
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.

2 participants