cli/api
Mislav Marohnić 04f20ddb2b Use statusCheckRollup internal GraphQL to simplify Statuses+Checks
With the old approach, we had to enumerate all StatusContexts and
CheckRuns to calculate whether a PR has passing or failing CI status.

Using `statusCheckRollup` which is behind the `pe_mobile` feature flag,
this is somewhat simpler because both StatusContexts and CheckRuns are
now behind the same connection.

Additionally, should we decide to *not* show the number of
passing/failing checks, this now approach allows us to consume the
`statusCheckRollup { state }` field and avoid paginated collections
and calculating the "winning" state altogether.
2019-11-15 11:43:00 +01:00
..
client.go Customizable API client 2019-10-29 21:07:03 +01:00
client_test.go Add mising files 2019-10-29 21:19:34 +01:00
fake_http.go Add mising files 2019-10-29 21:19:34 +01:00
queries.go Use statusCheckRollup internal GraphQL to simplify Statuses+Checks 2019-11-15 11:43:00 +01:00
queries_issue.go Add issue create test 2019-11-08 15:20:24 +01:00
queries_repo.go Add issue create test 2019-11-08 15:20:24 +01:00