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]

Warning

Rate limit exceeded

@MantisClone has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 19 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 1765cfe and 017afdb.

📒 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 that automatically manages project board items for the RequestNetwork/integration-demo repository. The workflow triggers when issues are opened or PRs are opened, and delegates the logic to a reusable workflow defined in the RequestNetwork/.github repository.

The implementation is straightforward and follows best practices: it uses event-based triggers appropriate for project management automation, delegates complex logic to a shared reusable workflow (promoting code reuse and maintainability), and securely passes the required PROJECT_TOKEN via GitHub secrets. The workflow correctly targets issues (opened), pull requests (opened), and conditionally adds items based on whether PRs have linked issues—avoiding duplication on the project board.

Key consideration: The reusable workflow reference uses @main which means any updates to RequestNetwork/.github will automatically apply here. This is beneficial for receiving improvements but could introduce breaking changes if the upstream workflow changes unexpectedly. The repository must have the PROJECT_TOKEN secret configured for this workflow to function.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk. The workflow is syntactically correct and follows GitHub Actions best practices.
• Score of 4 reflects a well-implemented, straightforward change with correct syntax and proper use of GitHub Actions patterns. The primary consideration preventing a perfect score is the use of @main for the reusable workflow reference, which could introduce unexpected changes if the upstream repository makes breaking modifications. Additionally, the repository must have the PROJECT_TOKEN secret configured for this to function, which is an operational requirement rather than a code issue. These are not blockers but operational considerations for successful deployment.
• No files require special attention. The workflow file is minimal, correct, and properly structured.

Important Files Changed

Filename	Overview
.github/workflows/auto-project.yml	New workflow file that automatically adds issues and PRs (without linked issues) to the project board. Calls a reusable workflow from RequestNetwork/.github using @main branch ref. Requires PROJECT_TOKEN secret to be configured in the repository. The workflow is minimal, correct, and follows GitHub Actions conventions.

Sequence Diagram

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

    User->>Event: Opens Issue or PR
    Event->>Workflow: Triggers (issues:opened or pull_request:opened)
    Workflow->>ReusableWF: Call reusable workflow with PROJECT_TOKEN
    ReusableWF->>ReusableWF: Check if PR has linked issue
    alt PR with linked issue
        ReusableWF->>ReusableWF: Skip (track linked issue instead)
    else PR without linked issue or Issue
        ReusableWF->>ProjectAPI: Add to Project Board
        ProjectAPI-->>ReusableWF: Item added
    end
    ReusableWF-->>Workflow: Complete
    Workflow-->>Event: Workflow finished

Loading