chore: remove pull_request trigger from auto-project workflow

[MantisClone]

The reusable workflow now only handles issues. Remove unnecessary pull_request trigger.

Fixes RequestNetwork/public-issues#151

Summary by CodeRabbit

• Chores
  • Modified workflow automation to trigger on issue creation only, removing pull request event triggers.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A GitHub Actions workflow configuration file is updated to remove the pull_request trigger event. The workflow now only executes when issues are opened, eliminating unnecessary workflow runs that were previously triggered by pull request events.

Changes

Cohort / File(s)	Summary
GitHub Actions Configuration .github/workflows/auto-project.yml	Removed pull_request trigger block (types: [opened]); workflow now triggers only on issues trigger events

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing the pull_request trigger from the auto-project workflow.
Linked Issues check	✅ Passed	The pull request successfully removes the pull_request trigger from .github/workflows/auto-project.yml, exactly addressing the requirement in issue #151.
Out of Scope Changes check	✅ Passed	All changes are within scope; only the pull_request trigger block was removed from the auto-project workflow as required.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This PR removes the pull_request trigger from the auto-project workflow, leaving only the issues trigger. This aligns the workflow with its actual purpose and the reusable workflow it calls, which only handles issues.

• Removed pull_request trigger with types: [opened] from workflow triggers
• Workflow now only triggers on issues with types: [opened]
• Change is consistent with PR chore: add reopen-issue-if-prs-open workflow #29 which added a separate workflow for handling PRs related to issues

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The change is a simple, well-justified removal of an unnecessary trigger. The workflow originally included both issues and pull_request triggers, but the reusable workflow it calls (add-to-project.yml) only handles issues. Removing the pull_request trigger eliminates unused configuration and clarifies the workflow's purpose.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/auto-project.yml	Removed pull_request trigger, leaving only issues trigger - aligns with reusable workflow that handles issues only

Sequence Diagram

sequenceDiagram
    participant Issue as GitHub Issue
    participant Workflow as auto-project.yml
    participant Reusable as add-to-project.yml
    participant Project as GitHub Project

    Note over Issue,Project: Before: Triggered on issues AND PRs
    Note over Issue,Project: After: Triggered on issues ONLY

    Issue->>Workflow: Issue opened event
    activate Workflow
    Workflow->>Reusable: Call reusable workflow
    activate Reusable
    Reusable->>Project: Add issue to project
    Project-->>Reusable: Success
    deactivate Reusable
    Reusable-->>Workflow: Complete
    deactivate Workflow

Loading