chore: remove pull_request trigger from auto-project workflow#7
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
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. 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 |
Greptile SummaryRemoved the
Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant GitHub
participant AutoProjectWorkflow
participant ReusableWorkflow
Note over AutoProjectWorkflow: Before: Triggered on issues AND pull_requests
Note over AutoProjectWorkflow: After: Triggered on issues ONLY
User->>GitHub: Opens new issue
GitHub->>AutoProjectWorkflow: Trigger (issues.opened)
AutoProjectWorkflow->>ReusableWorkflow: Call add-to-project.yml
ReusableWorkflow->>GitHub: Add issue to project
User->>GitHub: Opens new pull request
Note over GitHub,AutoProjectWorkflow: No longer triggers auto-project workflow
|
The reusable workflow now only handles issues. Remove unnecessary pull_request trigger.
Fixes RequestNetwork/public-issues#151