Skip to content

Fix merge conflict markers in setup files #3484

Fix merge conflict markers in setup files

Fix merge conflict markers in setup files #3484

Triggered via pull request March 27, 2026 01:04
Status Failure
Total duration 1m 3s
Artifacts

gemini-dispatch.yml

on: pull_request
dispatch
4s
dispatch
debugger
debugger
review  /  review
42s
review / review
invoke  /  invoke
invoke / invoke
triage  /  triage
triage / triage
triage  /  label
triage / label
fallthrough
5s
fallthrough
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
review / review
Invalid value. Matching delimiter not found 'EOF'
review / review
Unable to process file command 'output' successfully.
review / review
Process completed with exit code 1.
dispatch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
review / review
Gemini CLI stderr was not valid JSON
Input validation
No authentication method provided. Please provide one of 'gemini_api_key', 'google_api_key', or 'gcp_workload_identity_provider'.