mirror of
https://github.com/LBRYFoundation/lbry-desktop.git
synced 2025-09-20 18:09:51 +00:00
## Changes 1. Add hint on adding "Closes", "Fixes", etc. keywords to directly update the Issue state when the PR gets merged 2. Collapse "PR Checklist" and "PR Type". - With the assumption that these 2 items are mainly reminders for contributors, and that reviewers will typically only look at it one time, we collapse these sections to reduce clutter in the PR description.
47 lines
1.4 KiB
Markdown
47 lines
1.4 KiB
Markdown
## Fixes
|
|
|
|
Issue Number:
|
|
|
|
<!-- Tip:
|
|
- Add keywords to directly close the Issue when the PR is merged.
|
|
- Skip the keyword if the Issue contains multiple items.
|
|
- https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword
|
|
-->
|
|
|
|
## What is the current behavior?
|
|
|
|
## What is the new behavior?
|
|
|
|
## Other information
|
|
|
|
<!-- If this PR contains a breaking change, please describe the impact and solution strategy for existing applications below. -->
|
|
|
|
## PR Type & Checklist
|
|
|
|
<details><summary>PR Type...</summary>
|
|
|
|
What kind of change does this PR introduce?
|
|
|
|
- [ ] Bugfix
|
|
- [ ] Feature
|
|
- [ ] Code style update (formatting)
|
|
- [ ] Refactoring (no functional changes)
|
|
- [ ] Documentation changes
|
|
- [ ] Other - Please describe:
|
|
|
|
</details>
|
|
|
|
<!---------------------------------------------------------------------------->
|
|
|
|
<details><summary>PR Checklist...</summary>
|
|
|
|
<!-- For the checkbox formatting to work properly, make sure there are no spaces on either side of the "x" -->
|
|
|
|
Please check all that apply to this PR using "x":
|
|
|
|
- [ ] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
|
|
- [ ] I added a line describing my change to CHANGELOG.md
|
|
- [ ] I have checked that this PR does not introduce a breaking change
|
|
- [ ] This PR introduces breaking changes and I have provided a detailed explanation below
|
|
|
|
</details>
|