Detach Issues from Pull Requests

How the Repo Maintainer can Detach Issues from Pull Requests

In GitHub, issues and pull requests may automatically link when specific keywords (e.g., "close", "fixes") are used in pull request descriptions or comments. This guide explains how to detach an issue from a pull request.

Steps to Detach an Issue from a Pull Request

1. Navigate to the Pull Request - Click on the Pull Requests tab and locate the pull request linked to the issue.

1. Remove the Linking Keyword - Open the pull request description or comments where the link to the issue is mentioned. - Look for keywords like close #issue_number, fixes #issue_number, or resolves #issue_number. - Remove these keywords or replace them with plain text (e.g., related to #issue_number).

1. Update the Pull Request Description - After editing the description or comments, click the Save or Update Comment button to confirm your changes. 👇

1. Verify the Detachment - Navigate to the issue that was previously linked. - Confirm that the issue is no longer listed under the Linked pull requests section.

   1. You can also make changes to the issue description.

❌Before Removing the Issue Link from the PR Body ❌

✅After Removing the Issue Link from the PR Body ✅

---

After removing the issue link from the PR body, refresh the page to see the changes reflected in the PR interface. The previously linked issue will no longer appear in the related issues section.

• Learn more about issue-PR relationships here

Detaching the issue does not delete any comments or history.

• Removing the linking keyword ensures that the issue and pull request are no longer automatically linked.

• If the pull request has already been merged, the link cannot be removed.

Lightning Bounties Considerations

• Bounty Tracking: Lightning Bounties tracks issue and PR status via GitHub integration. Unlinking an issue from a PR may affect bounty eligibility or payout triggers if the bounty is configured to require a linked/closed issue.

• Workflow: Always coordinate with your team and check Lightning Bounties documentation if you're unsure how unlinking affects bounty status.

• Permissions: Lightning Bounties only has read-only access to your repository and cannot modify links on your behalf.

---

Best Practices

• Double-check PR descriptions for linking keywords before submitting.

• Communicate with contributors if unlinking may impact bounty rewards.

• For merged PRs, note that links are part of the permanent record; only open PRs can be edited to change links.

• For more details, refer to GitHub’s official documentation on managing issues and pull requests.

• _{If you have additional questions, feel free to reach out to the repository maintainers or send a note to the Lightning Bounties Discord}