cli/command
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
..
completion.go Add tests 2019-10-31 23:43:50 +01:00
completion_test.go Add tests 2019-10-31 23:43:50 +01:00
issue.go Swap "open in browser" to "view in browser" for view cmd 2019-11-13 13:59:32 -07:00
issue_test.go Add issue create test 2019-11-08 15:20:24 +01:00
pr.go Merge pull request #63 from github/branch-from-fork 2019-11-15 09:28:00 +01:00
pr_create.go Avoid re-wrapping of "could not determine suitable remote" error 2019-11-14 19:31:33 +01:00
pr_create_test.go Add pr create test for git clean state 2019-11-13 19:25:02 +01:00
pr_test.go Use OWNER:BRANCH syntax for cross-repo PRs 2019-11-14 16:46:59 +01:00
root.go Use statusCheckRollup internal GraphQL to simplify Statuses+Checks 2019-11-15 11:43:00 +01:00
testing.go 🔥 last instance of mockOpenInBrowser 2019-11-06 19:41:18 +01:00