Feature request: cross-links between PRs within an organization #108316
Unanswered
KIVagant
asked this question in
Pull Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Body
Hi. Please excuse me if this is the wrong space for such questions.
I'll keep it short. When I create Pull Requests working on a big change, I usually spend a lot of time putting links to PR descriptions to inter-connect them.
I.e., in PR
projectA#1
, I add links to related PRs inprojectB#3
,projectB#4
,projectC#114
etc. And then I do the same for every other PR to mentionprojectA#1
, and all other related changes. The bigger is the change, the more PRs it takes, the more time I have to spend adding more and more links. Including links to already closed and/or merged PRs. Would be really helpful, if GitHub somehow find such changes and shows related PRs automatically. This could be done based on some clues, such as similarity in PR titles or GitHub labels. In my case, I always add ticket numbers using square brackets, like:[TICKET-123][TICKET-124] Made the combined change
. Other projects, may not use brackets, but still have ticket numbers like in this example.Unfortunately, there's no standard way of mentioning tickets or any other traits that connect PRs. That's why this feature request may need a proper discussion first. I believe, there can be at least some way of connecting code changes from different repositories even if this will require following some naming or formatting patterns, offered by GitHub itself.
Beta Was this translation helpful? Give feedback.
All reactions