Resolve a pull request review thread with:
vk resolve https://github.com/leynos/vk/pull/191#discussion_r123456789
The resolver uses GitHub GraphQL. When vk is built with the
unstable-rest-resolve feature, -m or --message posts a reply before
resolving:
vk resolve https://github.com/leynos/vk/pull/191#discussion_r123456789 \
--message "Addressed in the latest commit."
To find the thread, the resolver queries the pull request's reviewThreads
connection and scans the first 100 comments in each thread for the requested
fullDatabaseId. A comment beyond the first 100 comments of a thread is not
found.
--http-timeout SECS sets the total deadline for the REST reply request,
including connection, request, and response handling; its default is 10 seconds.
--connect-timeout SECS sets the connection deadline; its default is 5
seconds. A 404 response from the reply endpoint emits a warning and continues
with GraphQL resolution. Any other non-2xx response or a timeout aborts before
GraphQL resolution, retaining the reply route and status or deadline details in
the diagnostic.
GraphQL networking limitations
The GraphQL client sends requests directly through Hyper and rustls. It does
not honour the HTTP_PROXY or HTTPS_PROXY environment variables, and it does
not follow redirects. Use a directly reachable GraphQL endpoint; this
deliberate transport boundary is recorded in
ADR 001 and explained in the
GraphQL transport migration guide.