fix: add checkout to release job and use DISPATCH_TOKEN#3
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
Two fixes to the riscv64 build workflow:
Add
actions/checkout@v4to thereleasejob —gh release createneeds a git repository context to work. Without checkout, the job fails
with
fatal: not a git repository.Use
DISPATCH_TOKENinstead ofGITHUB_TOKENin thenotify-indexjob —
GITHUB_TOKENis scoped to this repo only and cannot triggerrepository_dispatchon the central wheels repo. Also removes|| trueso errors surface in CI logs.
Setup required
Add
DISPATCH_TOKENsecret to this repo (PAT withrepo+workflowscopes).