ci: dispatch checks for release pull requests - #170
Merged
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5b868c22d1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



PR Checklist
Does this PR introduce a breaking change?
Problem
Resources created with the default
GITHUB_TOKENdo not emit recursive workflow runs. A plain dispatch can run CI on the release branch, butworkflow_dispatchhas no native pull-request event context for SonarCloud.Changes
workflow_dispatchwith required string inputs for PR number, head ref, and base refactions: writeplus the documented release permissions--repo, the release PR head ref, and string-safe--raw-fieldinputssonar.pullrequest.key,sonar.pullrequest.branch, andsonar.pullrequest.basearguments on dispatched runsVerification
deno task format:checkgit diff --checkThe flow uses the default short-lived token and does not reintroduce a PAT or repository token secret.