Skip to content

Conversation

@MantisClone
Copy link
Member

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

Fixes RequestNetwork/public-issues#131

@coderabbitai
Copy link

coderabbitai bot commented Jan 19, 2026

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 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 4ec9359 and 0a67d0c.

📒 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

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

@greptile-apps
Copy link

greptile-apps bot commented Jan 19, 2026

Greptile Summary

Added workflow that automatically reopens issues when they are closed while linked pull requests remain open. This prevents premature issue closure and ensures issues stay tracked until all related work is completed. The workflow follows the same reusable workflow pattern as the existing auto-project.yml workflow.

  • Uses centralized reusable workflow from RequestNetwork/.github repository
  • Triggers on issue closure events
  • Requires REOPEN_ISSUES_TOKEN secret with appropriate permissions

Confidence Score: 5/5

  • This PR is safe to merge with minimal risk
  • The workflow is minimal, well-structured, and follows the established pattern from auto-project.yml. It delegates to a reusable workflow in the organization's central repository, reducing maintenance burden. The change is non-invasive and only triggers on issue closure events.
  • No files require special attention

Important Files Changed

Filename Overview
.github/workflows/reopen-issue-if-prs-open.yml Added workflow to reopen closed issues when linked PRs remain open, preventing premature issue closure

Sequence Diagram

sequenceDiagram
    participant User
    participant Issue
    participant Workflow as Reopen Workflow
    participant ReusableWorkflow as RequestNetwork/.github
    participant GitHub API
    
    User->>Issue: Close issue
    Issue->>Workflow: Trigger on closed event
    Workflow->>ReusableWorkflow: Call reusable workflow
    ReusableWorkflow->>GitHub API: Check linked PRs
    alt PRs still open
        GitHub API-->>ReusableWorkflow: Return open PRs
        ReusableWorkflow->>GitHub API: Reopen issue
        GitHub API-->>Issue: Issue reopened
    else No open PRs
        GitHub API-->>ReusableWorkflow: No open PRs found
        ReusableWorkflow-->>Issue: Keep closed
    end
Loading

@MantisClone MantisClone self-assigned this Jan 19, 2026
@MantisClone MantisClone merged commit 97ca09a into main Jan 20, 2026
6 checks passed
@MantisClone MantisClone deleted the chore/add-reopen-issue-workflow branch January 20, 2026 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Automation] - Issues close prematurely when first PR in a stack merges

2 participants