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
Tools like Dpulls and Mergify support expressing dependencies between pull requests using metadata in the PR description (although sadly not currently using a syntax that works across both tools).
Edit: Dpulls now also supports the Depends-On: syntax of Mergify.
This results in statuschecks on the PR, preventing merging until the dependencies are satisfied.
It would be helpful if the Aviator CLI automatically added this metadata to the descriptions of PRs in the stack. I haven't used Aviator itself yet, only the CLI standalone, but had a quick look in the Aviator docs on CI Status Requirements and couldn't see anything similar about status checks that Aviator adds, but that would also be useful I think.
The text was updated successfully, but these errors were encountered:
Hi @joehorsnell, apologies for the delay. Thanks for submitting the feature request. Are you looking to use av CLI alongside Dpulls or are you looking to use Aviator service for managing CI requirement?
We currently do not have support for Depends-On: but want to understand if you are looking for this support only in av CLI or also in the Aviator service?
Tools like Dpulls and Mergify support expressing dependencies between pull requests using metadata in the PR description (although sadly not currently using a syntax that works across both tools).
Edit: Dpulls now also supports the
Depends-On:
syntax of Mergify.This results in status checks on the PR, preventing merging until the dependencies are satisfied.
It would be helpful if the Aviator CLI automatically added this metadata to the descriptions of PRs in the stack. I haven't used Aviator itself yet, only the CLI standalone, but had a quick look in the Aviator docs on CI Status Requirements and couldn't see anything similar about status checks that Aviator adds, but that would also be useful I think.
The text was updated successfully, but these errors were encountered: