The update subcommand should support updating a single triage. This would make it easy to react to a triage event such as a user replying. The subcommand would take a backend system identifier (an issue number in GitHub's case) and only update that triage.
There are two ways it could run, both would need the triage id:
# Specifying the project:
vexflow update organization/repo --triage=3467
# ... or specifying the triage repo:
vexflow update --triage=3467 --triage-repo=organization/.vexflow
It cannot run only with the ID as vexflow needs to infer the triage repo.
The
updatesubcommand should support updating a single triage. This would make it easy to react to a triage event such as a user replying. The subcommand would take a backend system identifier (an issue number in GitHub's case) and only update that triage.There are two ways it could run, both would need the triage id:
It cannot run only with the ID as vexflow needs to infer the triage repo.