auto pr close

[prem7443]

Select Topic Area

Question

Body

is there any method when pr create if code conflict it was auto closed

[RubenMartinezSiso]

Hi @prem7443!

In GitHub, there is no default behavior or built-in setting that automatically closes a pull request (PR) if it has merge conflicts. Merge conflicts are a common part of collaborative development, and GitHub generally expects developers to resolve them manually before a PR can be merged. A PR with conflicts simply shows a warning indicating that it "can't be merged automatically," but it remains open and awaits resolution.

That said, it's possible to automate the closing of pull requests with conflicts using GitHub Actions or other CI/CD workflows. For example, a GitHub Action can be set up to detect when a pull request becomes unmergeable (due to conflicts with the base branch) and then automatically close it. This, however, requires explicit configuration and scripting on your part. GitHub provides APIs and webhook events that allow you to track PR status changes and perform such actions programmatically.

It’s important to consider the implications of automatically closing PRs. In most projects, conflicts are resolved through rebase or merge, and closing a PR outright could mean losing valuable contributions unless they are reopened or recreated. For that reason, most teams prefer to notify the developer through comments or CI checks rather than closing the PR.

[prem7443]

so that means it was not possible

[LqhResearch]

Hi! 👋 Great question — I think you're asking whether it's possible to automatically close a PR when it has merge conflicts. Here's a breakdown:

GitHub doesn’t auto-close PRs with merge conflicts by default.
Merge conflicts are common during active development, and GitHub keeps the PR open so contributors can resolve them manually.

However, you can implement automation with GitHub Actions to close PRs that have merge conflicts. For example, a bot can check for conflicts and auto-close the PR with a comment.

Here’s a general idea:

• Use a GitHub Action that:

  1. Runs on pull_request event.
  2. Checks if the PR has merge conflicts.
  3. If so, uses the GitHub API to close it and optionally comment.

There are some community actions or you could write a custom script using the REST API.

But keep in mind:
Automatically closing PRs might frustrate contributors — especially if it’s a minor conflict that’s easy to fix. A friendlier approach is to notify them first (e.g., with a comment or label) and give them a chance to resolve it.

Let me know if you'd like an example GitHub Action for this! Happy to help set it up. 😊

[prem7443]

yes help me to write action file

[LqhResearch]

@prem7443 Hi, Please refer to this code

name: Auto Close Conflicted PRs

on:
  pull_request:
    types: [opened, synchronize, reopened]

jobs:
  check-mergeability:
    runs-on: ubuntu-latest

    steps:
      - name: Check PR mergeability
        uses: actions/github-script@v7
        with:
          script: |
            const pr = await github.rest.pulls.get({
              owner: context.repo.owner,
              repo: context.repo.repo,
              pull_number: context.payload.pull_request.number
            });

            const isMergeable = pr.data.mergeable;

            // GitHub may return `null` for mergeable if it's still calculating.
            if (isMergeable === false) {
              // Leave a comment
              await github.rest.issues.createComment({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: context.payload.pull_request.number,
                body: '⚠️ This pull request has merge conflicts and will be closed automatically. Please resolve the conflicts and create a new PR if needed.'
              });

              // Close the PR
              await github.rest.pulls.update({
                owner: context.repo.owner,
                repo: context.repo.repo,
                pull_number: context.payload.pull_request.number,
                state: 'closed'
              });
            } else if (isMergeable === null) {
              // Try again later by failing this job (so it can be retried manually or re-run by PR update)
              core.setFailed('Mergeability is unknown at this time. Try again later.');
            } else {
              console.log('PR is mergeable. No action needed.');
            }

Automatically closing PRs can be a turn-off for contributors. Consider using it only for automated branches/PRs (bots), or use a label + warning instead of closing them outright.

Hope it helps you.

[prem7443]

are u unable to help me

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬