chore: add reopen-issue-if-prs-open workflow

[MantisClone]

Adds workflow that reopens issues when closed while linked PRs are still open.

Fixes RequestNetwork/public-issues#131

[coderabbitai]

Warning

Rate limit exceeded

@MantisClone has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 29 minutes and 34 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 15dae97 and 45dac37.

📒 Files selected for processing (1)

• .github/workflows/reopen-issue-if-prs-open.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 new GitHub workflow that automatically reopens issues when they are closed while linked PRs are still open. The workflow follows the established delegation pattern used elsewhere in the project (similar to auto-project.yml), delegating the actual implementation to a centralized workflow in the RequestNetwork organization's .github repository. The workflow configuration itself is correct and minimal, triggering on closed issues and passing the necessary secret for authentication. The feature addresses issue RequestNetwork/public-issues#131.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk. The workflow configuration is correct and follows established patterns.
• The workflow file is minimal and correct, following the same delegation pattern as auto-project.yml. Score is 4/5 rather than 5/5 because: (1) the actual implementation logic resides in an external RequestNetwork/.github repository that cannot be reviewed in this PR, (2) there is no documentation added to README.md explaining the new workflow for users, and (3) the commit message references an external issue but provides no details about requirements or behavior."
• No files require special attention from a code perspective, but documentation for this new workflow would be beneficial for users.

Important Files Changed

Filename	Overview
.github/workflows/reopen-issue-if-prs-open.yml	New GitHub workflow that triggers on closed issues and delegates to a centralized reopen logic in RequestNetwork/.github repository. Follows established delegation pattern used by auto-project.yml. Configuration is straightforward and correct, though the actual implementation exists in an external repository that cannot be reviewed here.

Sequence Diagram

sequenceDiagram
    participant GitHub as GitHub Issues
    participant Workflow as reopen-issue-if-prs-open.yml
    participant Central as RequestNetwork/.github<br/>(reopen-issue-if-prs-open.yml)
    participant API as GitHub API

    GitHub->>Workflow: Issue closed event
    Workflow->>Central: Call reusable workflow<br/>with REOPEN_ISSUES_TOKEN
    Central->>API: Query issue PRs
    API-->>Central: PR data (open/closed status)
    Central->>Central: Check if any linked PRs<br/>are still open
    alt PRs Still Open
        Central->>API: Reopen issue
        API-->>Central: Issue reopened
    else All PRs Closed
        Central-->>Central: No action needed
    end
    Central-->>Workflow: Workflow complete
    Workflow-->>GitHub: Update status

Loading