quotidian-ennui / gh-my

Show open issues/PR in your repos

About Me

Sometimes I have things to say; you can find my assorted ramblings for your reading pleasure here.

I have excellent knowledge of many different technology stacks, and can recognise potential weaknesses and design effective solutions. I understand the interplay between new features, system complexity, and technical debt, and can make trade-offs among them effectively to deliver the solution you need.

---

gh-my's Issues

gh notifs hyperlink isn't terminated correctly if output is truncated

Cause: cli/go-gh#150

gh my prs fails if a repo does not have status checks

bsh ❯ gh my prs -a
template: :9:31: executing "" at <.statusCheckRollup.state>: nil pointer evaluating interface {}.state

This is because of quotidian-ennui/jubilant-octo-journey#2 since that repo does not have an status checks or workflows associated with it.

Add --jsonlines support to other sub commands

#46 adds --jsonlines support to gh my reviews

This could easily be added to the other sub commands that also use $TEMPLATE since the template is the same, the to_json would be the same.

• query_issues
• query_prs
• query_reviews
• query_workload

Probably a simple query for gh_vulns since we just need to push the 'nameWithOwner' from the query into the vulnerabilityAlerts section.

deployments URL is not the action run URL

bsh ❯ ./gh-my deployments -o telus-agcg -t tpm-demeter
Repo                                   ID           Env            Actionable  URL                                                                        When
telus-agcg/tpm-demeter-terraform-test  14505914355  main-approval  false       https://github.com/telus-agcg/tpm-demeter-terraform-test/runs/14505914355  3 days ago

bsh ❯ ./gh-my deployments -r telus-agcg/retro-cdc
ID          URL                                                              Branch  When
5388868900  https://github.com/telus-agcg/retro-cdc/actions/runs/5388868900  main    32 minutes ago

• If you click use the first link, you have to "use the LH menu to go back a step to approve"
  • The link where you can approve from is actually https://github.com/telus-agcg/tpm-demeter-terraform-test/actions/runs/5357752484
• If you use the second link (generated by gh run list then you can approve directly without navigating to a different screen

deployments -r filter isn't always reliable

A PR merge did not show up : https://github.com/telus-agcg/retro-cdc/actions/runs/5382086545
A manual workflow dispatch run did : https://github.com/telus-agcg/retro-cdc/actions/runs/5388868900

The repository in question doesn't have "required checks" so this might be the problem so check-runs for a PR merge doesn't exist?

gh run list -R "telus-agcg/retro-cdc" -s "waiting" is still more reliable so maybe we should just switch to that when a repository is requested?

gh my deployments

{
  search(
    query: "org:telus-agcg topic:tpm-demeter"
    type: REPOSITORY
    first: 100
    
  ) {
    edges {
      node {
        ... on Repository {
          nameWithOwner
          defaultBranchRef {
            target {
              ... on Commit {
                checkSuites(filterBy: {appId: 15368}, last: 1) {
                  nodes {
                    checkRuns(filterBy: {status: WAITING}, last: 1) {
                      nodes {
                        databaseId
                        url
                        pendingDeploymentRequest {
                          environment {
                            id
                            name
                          }
                          currentUserCanApprove
                          waitTimerStartedAt
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}