How to Delete a Pull Request in GitHub?

Pull requests (PRs) are an essential part of collaboration on GitHub, allowing developers to propose changes, review code, and discuss improvements before merging to the main codebase. However, sometimes a pull request might be opened by mistake, or it becomes unnecessary for other reasons. While GitHub does not allow you to “delete” a pull request in the traditional sense, there are some ways to manage an unwanted PR, including closing it or removing its content.

In this blog, we’ll explain the steps to handle an unwanted pull request on GitHub.

Key Points to Know About Pull Requests on GitHub

• Closing, Not Deleting: GitHub doesn’t offer a direct way to delete a pull request, but you can close it to prevent further activity.
• Merging and Archiving: If the changes are still needed, you can merge and archive the pull request. Alternatively, if a PR is no longer needed, it can simply be closed.
• Permission Requirements: Only those with write or admin access to the repository (or the original author of the PR) can close or modify a pull request.

How to Handle an Unwanted Pull Request

Option 1: Close the Pull Request

Closing a pull request is the most straightforward way to handle one that you no longer need. Closing prevents any further changes or discussions from happening within that PR.

1. Open the Pull Request on GitHub:
   Navigate to the repository, click on the Pull Requests tab, and select the unwanted pull request.
2. Close the Pull Request:
   In the pull request view, locate the Close pull request button at the bottom of the page.
3. Optional: Add a Comment:
   You can add a comment explaining why the pull request is being closed. This is a good practice, especially when collaborating, so others understand the reasoning.
4. Confirm Closure:
   Once you close it, the PR will still be listed in your repository under “Closed” PRs but won’t actively affect the repository.

Option 2: Remove the Content of a Pull Request

If you want to clear a PR that includes sensitive data or incorrect information, you can remove the content by updating the branch associated with it.

1. Reset the Branch:
   Reset the branch associated with the pull request to the desired state using the command line.

   git checkout <branch-name>
   git reset --hard <commit-id>

Replace <branch-name> with the name of the branch the PR is using and <commit-id> with the commit you want the branch to reflect.

2. Force Push the Changes:
   Push the modified branch back to GitHub.

   git push --force

This will effectively wipe out the content of the PR, as it removes any unwanted changes while leaving the pull request in place.

Reopening a Closed Pull Request

If you closed a pull request and later decide you want it back, GitHub allows you to reopen it as long as you haven’t deleted the branch.

1. Navigate to the Closed Pull Requests:
   Go to the repository’s Pull Requests tab and select Closed.
2. Select and Reopen the Pull Request:
   Find the closed PR you want to reopen, open it, and click on the Reopen pull request button.

Best Practices for Managing Pull Requests on GitHub

1. Review Before Opening a PR: Make sure your PR is ready and that you’re targeting the correct branch to avoid creating unnecessary PRs.
2. Use Draft Pull Requests: If your PR is still a work in progress, consider opening a Draft PR. This can prevent accidental merging and communicate that it’s not yet ready for review.
3. Close with a Clear Message: If you’re closing a PR, especially one that others might be interested in, add a comment explaining why for greater transparency.
4. Protect Sensitive Information: If sensitive information was accidentally added to a PR, remove it by force-pushing a cleaned-up branch and then close the PR to prevent further access.

Conclusion

While GitHub doesn’t allow you to delete a pull request outright, closing it or resetting its content are effective ways to handle unwanted PRs. By following these steps, you can manage your PRs effectively, ensuring that only relevant code and changes are actively reviewed and merged into the project. By keeping your repository organized, you maintain a cleaner, more efficient workflow on GitHub.

Maintaining well-organized pull requests not only enhances collaboration but also minimizes clutter in your repository, making development smoother for everyone involved.