Replies: 2 comments 1 reply
-
Alternatively, if you think it would be difficult to force this branch naming convention on contributors, then the PR template could be appended with a section where the contributor needs to fill in the issue number. |
Beta Was this translation helpful? Give feedback.
-
I just noticed that the way to correctly link an issue from a PR is to use the keyword I'm not entirely sure whether to add this action because of the branch naming convention; most contributors might not follow it. We can experiment adding this. |
Beta Was this translation helpful? Give feedback.
-
Hi @bglamadrid !
I explored github actions lately and I found two useful actions/workflow what I also use in my personal project so I thought I share in case you are interested.
This one adds an issue link to a newly opened PR. It appends the PR description and adds a link to the issue (to the bottom by default). This also visible in the original issue because the issue was referenced in the PR so it's clear that the two are connected. There is one requirement that the PR branch has to be prefixed, by default with "issue-" and the issue number.
Source: https://github.com/tkt-actions/add-issue-links
My workflow file as an example:
Beta Was this translation helpful? Give feedback.
All reactions