You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Topic
Please select what topic your discussion is about.
Coding
Contribution
Languages
Setup
Other. Please specify:
Discussion
In the PR template in the "Relate issue" section, contributes often add this issue number. However they forget to use the keywords in order to close the related issue. If this doesn't happen the PR gets merged but issue will stay open and clutter the backlog.
I think its better to add a few keywords (or just one) to the PR template, so u guys wont have to cleanup the backlog.
An important question to ask is what do we do with PR's that make changes related to an issue but immediately not solve it? Just not link it? So the issue stay open until its actually solved by another PR.
An important question to ask is what do we do with PR's that make changes related to an issue but immediately not solve it? Just not link it? So the issue stay open until its actually solved by another PR.
I think this distinction should just be clarified in the PR template. Something to the effect of: 'If this pull request fully resolves the relevant issue, put "closes" before the issue number. Example: "closes #99999"'
Topic
Please select what topic your discussion is about.
Discussion
In the PR template in the "Relate issue" section, contributes often add this issue number. However they forget to use the keywords in order to close the related issue. If this doesn't happen the PR gets merged but issue will stay open and clutter the backlog.
I think its better to add a few keywords (or just one) to the PR template, so u guys wont have to cleanup the backlog.
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
The text was updated successfully, but these errors were encountered: