Skip to content

GitHub PowerShell

The module serves as a wrapper around GitHub's REST API, making the functionalities and data available on GitHub accessible through PowerShell functions and classes. This module is tailored for developers, administrators, and GitHub enthusiasts who are familiar with PowerShell and want to integrate or manage GitHub seamlessly.

Desired supported scenarios

  • Support operators of personal repos, organization repos, and enterprise repos. -> Similar to the GitHub CLI, but with more commands.
  • Help operators that have multiple account and is a member of multiple organizations/enterprises. -> Similar to the GitHub CLI.
  • A context aware module that knows what environment you are working in, both locally and in GitHub Actions. -> Similar to the Octokit.
  • Built to be a native companion with GitHub Actions with Workflow commands that you can use. -> Similar to the Octokit and github-scripts
  • A module that can be used in other PowerShell compatible automation environments, like FunctionApps. -> Similar to the Octokit.
  • A way to deploy, declare and manage resources in GitHub programmatically. -> Similar to Terraform and Pulumi.

Supported platforms

As the module is built with the goal to support modern operators (assumed to use a newer OS), GitHub Actions and FunctionApps, the module will only support the latest LTS version of PowerShell on Windows, macOS, and Linux.

Getting Started with GitHub PowerShell

To dive into the world of GitHub automation with PowerShell, follow the sections below.

Installing the module

Download and install the GitHub PowerShell module from the PowerShell Gallery with the following command:

Install-PSResource -Name GitHub -Repository PSGallery -TrustRepository

Logging on

Authenticate using your GitHub credentials or access tokens to begin executing commands. The module supports everything:

  • Personal authentication
  • User Access Tokens (UATs) for personal accounts using both GitHub Apps and OAuth Apps. You can also bring your own app, so you dont have to use ours.
  • Personal Access Tokens (PATs) using both classic and fine-grained scopes.
  • Programmatic authentication
  • GitHub Apps using the client ID and private key.
  • Installation Access Tokens (IATs) for CI/CD pipelines, scheduled tasks and automation from other systems, like FunctionApps.

Personal authentication - User access tokens

This is the recommended method for authentication due to access tokens being short lived. It opens a browser window and prompts you to log in to GitHub. Once you log in, you will be provided with a code that you need to paste into the PowerShell console. The command already puts the code in your clipboard. It uses a GitHub App to authenticate, which is more secure than using a personal access token. The GitHub App is only granted access to the organizations or repositories you install it on. Visit the GitHub Apps documentation to read more about GitHub Apps. You can also use a different GitHub App to issue user access tokens, check the section on Using a different GitHub App for issuing User access tokens for more information.

Connect-GitHubAccount
! We added the code to your clipboard: [AB55-FA2E]
Press Enter to open github.com in your browser...:  #-> Press enter and paste the code in the browser window
✓ Logged in as octocat!

After this you will need to install the GitHub App on the repos you want to manage. You can do this by visiting the PowerShell for GitHub app page.

Info: We will be looking to include this as a check in the module in the future. So it becomes a part of the regular sign in process.

Consecutive runs of the Connect-GitHubAccount will not require you to paste the code again unless you revoke the token or you change the type of authentication you want to use. Instead, it checks the remaining duration of the access token and uses the refresh token to get a new access token if its less than 4 hours remaining.

Connect-GitHubAccount
✓ Access token is still valid for 05:30:41 ...
✓ Logged in as octocat!

This is also happening automatically when you run a command that requires authentication. The validity of the token is checked before the command is executed. If it is no longer valid, the token is refreshed and the command is executed.

Connect-GitHubAccount
⚠ Access token remaining validity 01:22:31. Refreshing access token...
✓ Logged in as octocat!

If the timer has gone out, we still have your back. It will just refresh as long as the refresh token is valid.

Connect-GitHubAccount
⚠ Access token expired. Refreshing access token...
✓ Logged in as octocat!

Personal authentication - User access tokens with OAuth app

This uses the same flow as above, but instead of using the GitHub App, it uses an OAuth app with long lived tokens. During the signing you can also authorize the app to access your private repositories. Visit the OAuth apps documentation to read more about OAuth apps on GitHub.

Connect-GitHubAccount -Mode OAuth

! We added the code to your clipboard: [AB55-FA2E]
Press Enter to open github.com in your browser...:
✓ Logged in as octocat!

Personal authentication - Personal Access Token

This is the least secure method of authentication, but it is also the simplest. Running the Connect-GitHubAccount command with the -UseAccessToken parameter will send you to the GitHub site where you can create a new personal access token. Give it the access you need and paste it into the terminal.

Connect-GitHubAccount -UseAccessToken
! Enter your personal access token: ****************************************
✓ Logged in as octocat!

Programmatic authentication - Installation Access Tokens (IATs)

The module also detects the presence of a system access token and uses that if it is present. This is useful if you are running the module in a CI/CD pipeline or in a scheduled task. The function looks for the GH_TOKEN and GITHUB_TOKEN environment variables (in order).

Connect-GitHubAccount
✓ Logged in as system!

You can also specify the token directly in the command.

Connect-GitHubAccount -Token '...'
✓ Logged in as octocat!

Using a GitHub App

If you are using a GitHub App, you can use the Connect-GitHubAccount command to authenticate using the client ID and private key.

Connect-GitHubAccount -ClientId 'lv123456789' -PrivateKey '-----BEGIN PRIVATE KEY----- ... -----END PRIVATE KEY-----'
✓ Logged in as my-github-app!

Using this approach, the module will autogenerate a JWT every time you run a command. I.e. Get-GitHubApp.

Using a different host

If you are using GitHub Enterprise, you can use the -Host (or -HostName) parameter to specify the host you want to connect to. This can be used in combination with all the other authentication methods.

Connect-GitHubAccount -Host 'https://github.local'
✓ Logged in as octocat!

Or you might be using GitHub Enterprise Cloud with Data Residency.

Connect-GitHubAccount -Host 'https://msx.ghe.com'
✓ Logged in as octocat!

Using a different GitHub App for issuing User access tokens

Instead of using our default GitHub App, you can use a different GitHub App to issue user access tokens. You can use the -ClientID parameters to specify the app you want to use.

Connect-GitHubAccount -Host 'https://msx.ghe.com' -ClientID 'lv123456789'
✓ Logged in as octocat!

Command Exploration

Familiarize yourself with the available cmdlets using the module's comprehensive documentation or inline help.

Get-Command -Module GitHub

References

Official GitHub Resources

General Web References

Inspiration Behind the Project

Authentication and Login

Module Configuration and Environment