I tried rooting around the documentation but didn’t find anything which seemed to cover these two issues.
We’re considering a “merge bot” à la bors and I was looking at ng as something which might fit, but:
We have multiple maintenance branches aside from the main development branch, we’d actually want to implement ng on the maintenance branches first, as it’s more important that they are not broken than the development one.
- does ng handles destination branches on PRs and merges into the correct destination?
- if it does, does ng use a staging branch for each destination (being able to queue PRs for e.g. 1.1 and 1.2 concurrently and independently)
- similar question for trying I guess, can ng generate multiple trying branches or is only one try valid at any one time?