Execute authenticate git command in the next step after @actions/checkout

[fmontada]

Hi team
As part of our CI/CD workflow we are using Lerna to handle our Javascript mono repo

So we build, test, deploy and tag/release every-time something get merge to master

Our question is using @actions/checkout@v2 it is posible to do not delete the Github token in order for us execute git authenticated commands for the tag/release ?

Cleaning the token make sense but could be great if there is a way to add a toggle for the cleanup in case the workflow need to execute git authenticate commands after the git checkout

58070a9

- uses: actions/checkout@v2
  with:
    token: {{OUR_TOKEN_WITH_GIT_TAG_PERMISION}}

[jsg2021]

Same as my issue. #166

[ericsciple]

@fmontada the input persist-credentials controls whether the token is persisted in the local git config. Does that help?

[gmazzo]

The doc states that persist-credentials is enabled by default. Is that accurate?

Because in the source code I'm seeing the opposite:
https://github.com/actions/checkout/blob/v2/src/input-helper.ts#L123

And I'm getting this when running a git push inside a Gradle task:

fatal: could not read Username for 'https://***.com': Device not configured

[ericsciple]

@gmazzo are you using actions/checkout@v2 or a different version?

[gmazzo]

Yes, I have it like this:

      - name: Checkout
        uses: actions/checkout@v2
        with:
          token: ${{ secrets.GPR_TOKEN }}

But, I just wanted to double-check, because if my understanding of the source code is that it's false by default, not true as the documentation states...

EDIT: reading this other thread #166 (comment), I've just realized the issue. It's a local config, not global one. That will explain why cloning from a third-party tool is not working. Thanks!

[ericsciple]

The default is true. The runner applies the default from the action yaml