Is there a way to tie issues together across repos...
# how-do-i
f
Is there a way to tie issues together across repos in an org, or even better, have some mechanism within stacks for this? Any type of coordination/synchronization would help a lot with releases and the likes šŸ™‚
p
Hmm could you expand?
f
For sure šŸ™‚ for example, we have two PRs, each on a different repo: • UI: https://github.com/rivet-gg/hub/pull/28 • Backend: https://github.com/rivet-gg/rivet/pull/177 As we can see in the UI repo PR, it mentions "Related: rivet-gg/rivet#177". Both PRs are developing as part of the same feature, but need to be separated based on the repo. It would be nice if there was some kind of way to link them more strongly (one couldn't be merged until the other was approved let's say, or merging one merges the other)
p
Ahh yes we've thought about this and have plans to add the ability to create "manual dependencies" in the way that you're describing right from the Graphite UI :')
cc @Tomas Reimers
f
I think there could be some really helpful tooling around this that Graphite enforces. In the same way that PRs are a concept that GitHub has but Git doesn't, Graphite is definitely in a place to add this abstraction.
t
Ah yes, we have a V1 coming out in Jan :) I believe @kush will be implementing!
p
@Forest Anderson we've shipped automations! Give it a try and let us know what you think šŸ™‚