chore: remove pull_request trigger from auto-project workflow - #120
Conversation
|
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 SummaryRemoves the
Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Events
participant WF as auto-project.yml
participant RW as Reusable Workflow<br/>(add-to-project.yml)
Note over GH,RW: Before this PR
GH->>WF: issue opened
WF->>RW: Trigger workflow
GH->>WF: pull_request opened
WF->>RW: Trigger workflow (no-op)
Note over GH,RW: After this PR
GH->>WF: issue opened
WF->>RW: Trigger workflow
GH--xWF: pull_request opened (no longer triggers)
|
The reusable workflow now only handles issues. Remove unnecessary pull_request trigger.
Fixes RequestNetwork/public-issues#151