ghtool

Crates.io rust

ghtool is a command-line tool, created to provide easy access and interaction with GitHub Actions checks. It allows developers to quickly identify failing tests, linting issues, and build errors directly from the terminal. Reduces the need for manually sifting through logs and navigating the GitHub UI.

Especially useful when working with large codebases where test suite runs sharded across multiple jobs.

See the demo.

Key features

Installation

Rust toolchain is required. Install it from rustup.rs.

sh cargo install ghtool

Setup

ghtool requires a GitHub access token to access the GitHub API. The token is stored in the system keychain. The token is only used to access the GitHub API and is not used for any other purpose.

To authenticate ghtool with GitHub API, run:

sh ght login

For details on why the repo scope is needed: On required permissions

Usage

The tool is installed as executable ght for ease of use.

The tool is intended to be run in a repository, as it uses the current working directory to determine the repository to operate on. The current branch is used to determine which pull request to query.

``` Usage: ght [OPTIONS] [COMMAND]

Commands: test Get the failing tests for the current branch's pull request's checks lint Get lint issues for the current branch's pull request's checks build Get build issues for the current branch's pull request's checks login Authenticate ghtool with GitHub API logout Deauthenticate ghtool with GitHub API help Print this message or the help of the given subcommand(s)

Options: -v, --verbose Print verbose output -b, --branch Target branch; defaults to current branch -h, --help Print help -V, --version Print version ```

Configuration

The .ghtool.toml configuration file in your repository root is required. The file consists of three optional sections: test, lint, and build. Each section is used to configure the corresponding functionality of ghtool.

test

lint

build

Example

Here's an example .ghtool.toml file:

```toml [test] job_pattern = "(Unit|Integration|End-to-end) tests sharded" tool = "jest"

[lint] job_pattern = "Lint" tool = "eslint"

[build] job_pattern = "Typecheck" tool = "tsc" ```

Example usage

Check failing tests

``` % ght test ┌─────────────────────────────────────────────────────────────────────────────┐ │ Job: Unit tests sharded (2) │ │ Url: https://github.com/org/repo/actions/runs/5252627921/jobs/9488888294 │ └─────────────────────────────────────────────────────────────────────────────┘ FAIL src/components/MyComponent/MyComponent.test.tsx ● Test suite failed to run Error: Cannot read property 'foo' of undefined

  1 | import React from 'react';
  2 | import { render } from '@testing-library/react';
> 3 | import MyComponent from './MyComponent';
    | ^
  4 |
  5 | test('renders learn react link', () => {
  6 |   const { getByText } = render(<MyComponent />);

┌─────────────────────────────────────────────────────────────────────────────┐ │ Job: Unit tests sharded (3) │ │ Url: https://github.com/org/repo/actions/runs/5252627921/jobs/9488888295 │ └─────────────────────────────────────────────────────────────────────────────┘ FAIL src/components/AnotherComponent/AnotherComponent.test.tsx ● Test suite failed to run ... ```

Check lint issues

``` % ght lint ┌─────────────────────────────────────────────────────────────────────────────┐ │ Job: Lint │ │ Url: https://github.com/org/repo/actions/runs/5252627921/jobs/9488888294 │ └─────────────────────────────────────────────────────────────────────────────┘ @org/module:lint: /path/to/work/directory/src/components/component-directory/subcomponent-file/index.tsx @org/module:lint: 99:54 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any @org/module:lint: 109:46 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any @org/module:lint: 143:59 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any

@org/module:lint: /path/to/work/directory/src/components/another-component/ComponentTest.spec.tsx @org/module:lint: 30:33 warning Forbidden non-null assertion @typescript-eslint/no-non-null-assertion

@org/another-module:lint: /path/to/work/directory/src/components/DifferentComponent/ComponentTest.spec.tsx @org/another-module:lint: 2:18 error 'waitFor' is defined but never used @typescript-eslint/no-unused-vars ```

Run tests for failing test files

sh % ght test --files | xargs yarn test yarn run v1.22.19 $ NODE_ENV=test node ./node_modules/.bin/jest src/moduleA.test.ts src/moduleB.test.ts ...

Demo

https://github.com/raine/ghtool/assets/11027/13a012ac-a854-48a0-b514-9fcbd02c02aa

On required permissions

The tool currently uses Github's OAuth device flow to authenticate users. To access workflow job logs through OAuth, which lacks fine-grained permissions, the repo scope is required, granting scary amount of permissions.

Github App auth flow enables more fine grained permissions, but doesn't seem to work1 in the case where someone else than you owns the repository that is queried. Incidentally, the official GitHub CLI, which I used as reference, also uses OAuth flow with the repo scope and more (screenshot).

Feel free to reach out through issues if you know how to improve this.

1 This GraphQL query returns 200 but can't find the private repository: https://github.com/raine/ghtool/blob/master/ghtool/src/github/pullrequestfor_branch.graphql

Changelog

0.7.2 (26.08.2023)

0.7.0 (26.08.2023)