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.

[coderabbitai]

Warning

Rate limit exceeded

@MantisClone has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 29 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

📥 Commits

Reviewing files that changed from the base of the PR and between 6c39082 and ea38b5b.

📒 Files selected for processing (1)

• .github/workflows/auto-project.yml

---

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 to automatically add issues and pull requests to the RequestNetwork organization's project board. The workflow triggers on issue and PR opens, using a reusable workflow from RequestNetwork/.github and passing the PROJECT_TOKEN secret.

Key points:

• New workflow file is syntactically valid and follows GitHub Actions conventions
• Triggers are appropriately configured to handle issues and PRs
• Reusable workflow reference uses @main branch reference instead of pinning to a specific version, which could cause unexpected behavior changes
• Workflow requires PROJECT_TOKEN secret to be configured in repository settings
• Implementation aligns with the PR description regarding automatic project board management

Confidence Score: 3/5

• This PR is safe to merge with minor concerns about workflow versioning best practices.
• The workflow file is syntactically valid and implements the intended functionality properly. The main concern is the use of @main branch reference for the reusable workflow, which lacks version pinning and could lead to unexpected behavior changes if the shared workflow is updated. The workflow requires PROJECT_TOKEN secret to be configured, which is a dependency that should be verified before deployment. These are important operational considerations but not blocking issues.
• Ensure PROJECT_TOKEN secret is configured in repository settings before this workflow will function correctly.

Important Files Changed

Filename	Overview
.github/workflows/auto-project.yml	New GitHub workflow that automatically adds issues and pull requests to the project board. Uses a reusable workflow from RequestNetwork/.github with @main reference, which lacks version pinning and requires PROJECT_TOKEN secret to be configured.

Sequence Diagram

sequenceDiagram
    participant User
    participant GitHub as GitHub Event
    participant Workflow as auto-project.yml
    participant ReusableWF as RequestNetwork/.github<br/>(add-to-project.yml)
    participant ProjectAPI as GitHub Project API

    User->>GitHub: Open Issue or PR
    GitHub->>Workflow: Trigger workflow (on: opened)
    Workflow->>ReusableWF: Call reusable workflow with PROJECT_TOKEN
    alt Issue or PR without linked issue
        ReusableWF->>ProjectAPI: Add item to project board
        ProjectAPI-->>ReusableWF: Success
    else PR with linked issue
        ReusableWF-->>ReusableWF: Skip (linked issue tracked instead)
    end
    ReusableWF-->>Workflow: Complete
    Workflow-->>GitHub: Workflow completed

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

logic: The reusable workflow path uses @main which references the latest version of the shared workflow. This can cause unexpected behavior changes if the shared workflow is updated without this repository being aware of the changes. Consider pinning to a specific commit SHA (e.g., @abc1234) or tag version for reproducibility and to control when workflow behavior changes.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/auto-project.yml
Line: 11:11

Comment:
**logic:** The reusable workflow path uses `@main` which references the latest version of the shared workflow. This can cause unexpected behavior changes if the shared workflow is updated without this repository being aware of the changes. Consider pinning to a specific commit SHA (e.g., `@abc1234`) or tag version for reproducibility and to control when workflow behavior changes.

How can I resolve this? If you propose a fix, please make it concise.