chore: add auto-project workflow

[MantisClone]

Adds workflow to automatically add issues and PRs to the project board.

• Issues: Added when opened
• PRs without linked issues: Added when opened
• PRs with linked issues: Not added (the linked issue is tracked instead)

Uses the reusable workflow from RequestNetwork/.github.

---

Closes RequestNetwork/public-issues#130

[coderabbitai]

Walkthrough

A new GitHub Actions workflow is added at .github/workflows/auto-project.yml that automatically adds newly opened issues and pull requests to a project board. The workflow leverages an external action from RequestNetwork and retrieves the project token from repository secrets.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration \.github/workflows/auto-project\.yml	Adds new workflow triggered on issue and pull request creation events that automatically adds items to a project board using RequestNetwork action with PROJECT_TOKEN authentication

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a GitHub Actions workflow for automatic project management.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

---

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 adds a GitHub Actions workflow that automatically adds newly opened issues and pull requests to the organization's project board. The workflow delegates to a reusable workflow from RequestNetwork/.github that handles the logic for determining whether to add items based on whether PRs have linked issues.

• Clean implementation using a reusable workflow pattern
• Properly configured triggers for issue and PR opened events
• Correctly passes the required PROJECT_TOKEN secret

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The workflow is a simple, well-structured GitHub Actions configuration that uses a trusted reusable workflow from the organization's .github repository. It only adds automation for project management and has no impact on code execution or functionality.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/auto-project.yml	Adds workflow to auto-add issues and PRs to project board using reusable workflow

Sequence Diagram

sequenceDiagram
    participant User
    participant GitHub
    participant Workflow as auto-project.yml
    participant Reusable as RequestNetwork/.github<br/>add-to-project.yml
    participant Project as GitHub Project Board

    alt Issue Opened
        User->>GitHub: Create Issue
        GitHub->>Workflow: Trigger (on: issues.opened)
        Workflow->>Reusable: Call reusable workflow
        Note over Workflow,Reusable: Pass PROJECT_TOKEN secret
        Reusable->>Project: Add issue to project board
        Project-->>Reusable: Confirm added
    else Pull Request Opened (no linked issue)
        User->>GitHub: Create Pull Request
        GitHub->>Workflow: Trigger (on: pull_request.opened)
        Workflow->>Reusable: Call reusable workflow
        Note over Workflow,Reusable: Pass PROJECT_TOKEN secret
        Reusable->>Reusable: Check for linked issues
        Reusable->>Project: Add PR to project board
        Project-->>Reusable: Confirm added
    else Pull Request Opened (with linked issue)
        User->>GitHub: Create Pull Request<br/>(with linked issue)
        GitHub->>Workflow: Trigger (on: pull_request.opened)
        Workflow->>Reusable: Call reusable workflow
        Note over Workflow,Reusable: Pass PROJECT_TOKEN secret
        Reusable->>Reusable: Check for linked issues
        Reusable->>Reusable: Skip (issue already tracked)
    end

Loading

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In @.github/workflows/auto-project.yml:
- Line 11: The reusable workflow reference currently uses a mutable ref ("uses:
RequestNetwork/.github/.github/workflows/add-to-project.yml@main"); replace the
`@main` ref with an immutable tag or commit SHA (e.g., `@v1.2.3` or
`@<commit-sha>`) so the action is pinned; update the "uses" line to point to
that tag/SHA and ensure any CI docs or callers are updated to the chosen release
tag if needed.
- Around line 6-13: The job-level guard is using invalid syntax by referencing
secrets in the if: expression; update the add-to-project job to expose the
secret as a job-level env var (e.g., set env: HAS_PROJECT_TOKEN: ${{
secrets.PROJECT_TOKEN }}) and then change the if: condition to reference that
env var (e.g., if: ${{ env.HAS_PROJECT_TOKEN != '' }}), keeping the secrets:
PROJECT_TOKEN mapping for the reusable workflow; this preserves the secret usage
for the uses: RequestNetwork/... add-to-project job while avoiding direct secret
references in the if: expression.