Summary
GitHub work without the tab.
The everyday loop — find the repository, read the file, open the issue, raise the pull request — happens in one place, with what it is allowed to do decided by the token's scopes rather than by the tool.
What it is
A GitHub server written in TypeScript, sitting in a workspace alongside Workiva IGAM reporting scripts. It lists and searches repositories, reads files and directory listings, and covers issues and pull requests from listing through creation and updates.
What you get
- Repositories listed for a user or organization, searched across GitHub, and read in detail
- File contents and directory listings pulled out of a repository without cloning it
- Issues listed with filters, created with labels and assignees, and updated afterwards
- Issues and pull requests searched across GitHub
- Pull requests listed and created, drafts included
- User profiles read
Requirements
Node.js 16 or higher and a GitHub personal access token. The scopes decide what it can do: repo for private repositories and writes, public_repo for public ones, read:user and read:org for profile and organization data.