gh pr checks should show output summary of checks #5634

Activity

1. jgrumboe

   added

   enhancementa request to improve CLIa request to improve CLI

   on May 13, 2022
2. cliAutomation

   added

   needs-triageneeds to be reviewedneeds to be reviewed

   on May 13, 2022
3. samcoe

   added

   discussFeature changes that require discussion primarily among the GitHub CLI teamFeature changes that require discussion primarily among the GitHub CLI team

   and removed

   needs-triageneeds to be reviewedneeds to be reviewed

   on May 16, 2022
4. mislav commented on May 25, 2022

   

   mislav

   on May 25, 2022

   Contributor

   More actions

   Thanks for the feature request. We like this idea, and we agree that it would be useful to expose this text in the CLI. We're not sure about the name --summary, though, as "job summaries" are something different.

   I wonder which API field exposes the text Terraform plan has no changes come from. Might it be the title field?

   @jgrumboe Could you check by doing a manual API query on your end and report back:

   # 1. replace "123" with your PR number
   # 2. optionally replace "{owner}" and "{repo}" with your repository information
   gh api graphql -F owner='{owner}' -F repo='{repo}' -F pr=123 -f query='
   query ($owner: String!, $repo: String!, $pr: Int!) {
   	repository(owner: $owner, name: $repo) {
   		pullRequest(number: $pr) {
   			commits(last: 1) {
   				nodes {
   					commit {
   						statusCheckRollup {
   							state
   							contexts(first: 100) {
   								nodes {
   									__typename
   									... on CheckRun {
   										name
   										checkSuite {
   											workflowRun{workflow{name}}
   										}
   										text
   										title
   									}
   								}
   							}
   						}
   					}
   				}
   			}
   		}
   	}
   }
   '
5. mislav

   added

   help wantedContributions welcomeContributions welcome

   more-info-neededMore info needed from user/contributorMore info needed from user/contributor

   and removed

   discussFeature changes that require discussion primarily among the GitHub CLI teamFeature changes that require discussion primarily among the GitHub CLI team

   on May 25, 2022
6. jgrumboe commented on May 25, 2022

   

   jgrumboe

   on May 25, 2022

   ContributorAuthor

   More actions

   Hi @mislav

   The output for one example PR is as follows:

   {
     "data": {
       "repository": {
         "pullRequest": {
           "commits": {
             "nodes": [
               {
                 "commit": {
                   "statusCheckRollup": {
                     "state": "SUCCESS",
                     "contexts": {
                       "nodes": [
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         },
                         {
                           "__typename": "StatusContext"
                         }
                       ]
                     }
                   }
                 }
               }
             ]
           }
         }
       }
     }
   }
   

   Does this help?
7. mislav commented on Jun 21, 2022

   

   mislav

   on Jun 21, 2022

   Contributor

   More actions

   @jgrumboe Yeah that helps. Thank you!
8. mislav

   removed

   more-info-neededMore info needed from user/contributorMore info needed from user/contributor

   on Jun 21, 2022
9. mislav commented on Jun 27, 2022

   

   mislav

   on Jun 27, 2022

   Contributor

   More actions

   Possibly related report: #3739
10. jgrumboe commented on Jul 10, 2022

    

    jgrumboe

    on Jul 10, 2022

    ContributorAuthor

    More actions

    @mislav is there something I can help with?
11. sspaeth-r7 commented on Mar 28, 2023

    

    sspaeth-r7

    on Mar 28, 2023

    More actions

    I too agree this feature would be extremely helpful for a similar use case. Anything we can do to help?
12. vilmibm commented on Mar 28, 2023

    

    vilmibm

    on Mar 28, 2023

    Contributor

    More actions

    For tickets marked help wanted, feel free to announce intent to work on a thing and ask specific questions about implementation as needed.
13. jgrumboe commented on May 16, 2023

    

    jgrumboe

    on May 16, 2023

    ContributorAuthor

    More actions

    @vilmibm I created #7451 to add my requested feature. It was more than luck today that I read about GH_DEBUG=api and found this, for me, simple solution.
14. samcoe

    closed this as completedin #7451on Jul 6, 2023