chore: remove pull_request trigger from auto-project workflow#43
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 SummaryRemoved the
Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub
participant Workflow as auto-project.yml
participant Reusable as add-to-project.yml
participant Project as GitHub Project
Note over GH,Project: Before (with pull_request trigger)
GH->>Workflow: Issue opened event
Workflow->>Reusable: Call reusable workflow
Reusable->>Project: Add issue to project
GH->>Workflow: PR opened event
Workflow->>Reusable: Call reusable workflow
Note over Reusable: Reusable workflow only handles issues
Note over GH,Project: After (pull_request trigger removed)
GH->>Workflow: Issue opened event
Workflow->>Reusable: Call reusable workflow
Reusable->>Project: Add issue to project
Note over GH,Workflow: PR opened events no longer trigger workflow
|
The reusable workflow now only handles issues. Remove unnecessary pull_request trigger.
Fixes RequestNetwork/public-issues#151