This GitHub Action provides a way to configure credentials for any utility that uses the git command, or any utility that uses the git command as a subprocess, or any utility that uses the git configuration file in its authentication and cloning.

Authenticates using URL patterns that match https://server/prefix*. If no matching URL exists, the action will not use the authentication credentials presented via the github-personal-access-token input.

See here for some additional background on git config as it relates to the problem this action is solving, and here for general reference on git config from the official git documentation.

jobs:
    checkout:
        runs-on: ubuntu-latest
        steps:
            - name: Authorize
              uses: open-turo/action-git-auth@v2
              with:
                  github-personal-access-token:
                      ${{ secrets.PERSONAL_ACCESS_TOKEN }}

jobs:
    checkout:
        runs-on: ubuntu-latest
        steps:
            - name: Authorize
              uses: open-turo/action-git-auth@v2
              with:
                  server: githubenterprise.examplecompany.com
                  github-personal-access-token:
                      ${{ secrets.PERSONAL_ACCESS_TOKEN }}

jobs:
    checkout:
        runs-on: ubuntu-latest
        steps:
            - name: Authorize
              uses: open-turo/action-git-auth@v2
              with:
                  server: git.example.com
                  prefix: github-org
                  github-personal-access-token:
                      ${{ secrets.PERSONAL_ACCESS_TOKEN }}

This action is an node16 action.

This section describes how to develop the project.

In order to run tests for local development, first run npm install to download dependencies, and then run npm test to run the test suite. This library uses jest for its test suite.

In order for GitHub Actions to use this library, it must be packaged into the dist/ directory. As part of any pull request which changes the library, this should be run.

Run prepare:

npm run prepare  # Generate the dist/ files
git add dist/  # Add the dist/ files to the commit

Releases are created according to the Semantic Versioning process. We also use the Conventional Commits messages to determine what the release version is.

Once a PR has been merged, the repository maintainer is responsible for creating a new release, as well as moving the floating release tag to the new commit.

Please review Issues, post new Issues against this repository as needed.

Please see here for guidelines on how to contribute to this project.