Huon Wilson

Ah, the same applies to "manually" deferred annotations (i.e. an explicit string): ```python import strawberry from typing import Annotated @strawberry.type class Query: a: """Annotated["datetime", strawberry.lazy("datetime")]""" schema = strawberry.Schema(Query) ```

This seems like it overlaps conceptually with https://github.com/pantsbuild/pants/issues/18320 (and the `execution_dependencies`/`output_dependencies` split for `shell_command`/`adhoc_tool`), being all different sorts of different "kinds" of dependencies. I recall seeing a proposal (from @chrisjrn?)...

Oh, the name doesn't have to be the same as the repo? In that case, I guess this is just a doc issue.

(This could be used to remove the length lower-bound)

If the comments (or merge commit) include a reference to the PR number, github will put a link to that commit/comment in the PR, e.g. https://github.com/rust-lang/rust/pull/20997#ref-commit-e94a9f0 . These links are...

Is it possible to maybe detect that the parent of the current merge is the merge commit of the previous PR?

(And, if it isn't the right commit, wait a few seconds and try again?)

https://buildkite.com/stellar/stellargraph-public/builds/2442#_

https://buildkite.com/stellar/stellargraph-public/builds/2515 is similar, although `test_split_data_by_edge_type_and_attribute`

https://buildkite.com/stellar/stellargraph-public/builds/2729