chore: remove pull_request trigger from auto-project workflow#84
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 Issue as GitHub Issue
participant Workflow as Auto Add to Project Workflow
participant Reusable as RequestNetwork/.github Workflow
participant Project as GitHub Project
Note over Workflow: Triggers only on issues.opened
Issue->>Workflow: Issue opened event
Workflow->>Reusable: Call add-to-project.yml
Note over Reusable: Handles issue logic
Reusable->>Project: Add issue to project
Project-->>Reusable: Success
Reusable-->>Workflow: Complete
Note over Workflow: pull_request trigger removed
Note over Workflow: PRs no longer trigger this workflow
|
The reusable workflow now only handles issues. Remove unnecessary pull_request trigger.
Fixes RequestNetwork/public-issues#151