Skip to content

Latest commit

 

History

History
36 lines (24 loc) · 1.53 KB

README.md

File metadata and controls

36 lines (24 loc) · 1.53 KB
Raw

gh-tools

gh-find image

GitHub productivity tools

  • gh-purge-artifacts Purge GitHub Actions artifacts across GitHub repositories
  • gh-go-rdeps Find reverse Go dependencies across GitHub repositories
  • gh-find Walk file hierarchies across GitHub repositories
  • gh-pr Automate PR creation across GitHub repositories
  • gh-watch Manage notification subscriptions across GitHub repositories

Authentication

All tools require a GitHub personal access token in order to authenticate API requests and use following methods, in the order of precedence, to infer/set the token:

  • -token flag, in which case the user will be asked to enter the token interactively

  • GHTOOLS_TOKEN environment variable

  • GITHUB_TOKEN environment variable

  • ~/.config/gh-tools/auth.yml file, containing the token

    oauth_token: <token>

  • GitHub's official CLI tool gh configuration file, to avoid creating separate personal accesss tokens

Here's how you can create a personal access token.

Your personal access token may need the following scopes to use gh-tools:

  • repo
  • workflow
  • read:user

The explicit worklow scope is requred if you want to be able to make changes to GitHub Actions workflow files with gh-pr tool.