fix: use GitHub Actions API for workflow re-runs #327
Conversation
🤖 Worlddriven Status📊 Live Status Dashboard🗓️ Merge Date: 2025-12-24 at 17:00:03 UTC (today) 🎯 Want to influence when this merges?Your review matters! As a contributor to this project, your voice helps determine the merge timeline. How to review:
Your options:
💡 Pro tip: The more contributors who agree, the faster this gets merged! 📊 View detailed stats on the dashboard 📋 Recent Activity• 2025-12-22, 21:54:42 - Pull request opened This comment is automatically updated by worlddriven |
Replace Check Runs API with Actions API for re-running workflows after
accepting repository invitations. The Check Runs API is designed for
GitHub Apps while the Actions API properly re-runs GitHub Actions
workflows.
Changes:
- Use /actions/runs endpoint to find failed workflows by head SHA
- Use /actions/runs/{id}/rerun to trigger re-runs
- Filter for failed status to only re-run relevant workflows
TooAngel
force-pushed
the
fix/invitation-processor-rerun-api
branch
from
40845d8 to
26c4779
Compare
Summary
Fixes the invitation processor to correctly re-run GitHub Actions workflows after accepting repository invitations.
Problem
The previous implementation used the Check Runs API (
/check-runs/{id}/rerequest) which is designed for GitHub Apps, not GitHub Actions workflows.Solution
Switch to the GitHub Actions API:
GET /repos/{repo}/actions/runs?head_sha={sha}&status=failure- Find failed workflow runsPOST /repos/{repo}/actions/runs/{id}/rerun- Re-run the failed workflowsThis enables automatic CI re-runs on documentation PRs after worlddriven accepts repository invitations, allowing blocked PRs to proceed.