-
Notifications
You must be signed in to change notification settings - Fork 84
Unable to checkout repo with this action workflow #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you please setup a public repository that reproduces the problem? We can't help you with the information you provided. We use this action ourselves in conjunction with |
Hello @gr2m I have setup here, could you please have a look. I am trying checkout a private repo from the this repo https://github.com/iamatib/checkout-demo could you please have a look. Thanks in Advance. Regards, |
You are trying to checkout on: [workflow_dispatch]
jobs:
hello-world:
runs-on: ubuntu-latest
steps:
- uses: actions/create-github-app-token@v1
id: app-token
with:
app-id: ${{ vars.APP_ID }}
private-key: ${{ secrets.PRIVATE_KEY }}
+ repositories: 'checkout-test`
- name: Checkout Repository
uses: actions/checkout@v3
with:
token: ${{ steps.app-token.outputs.token }}
repository: iamatib/checkout-test |
Hello @gr2m Thank You, I thought when we give permissions for repo's in Github App, it should already be authenticated to run api's. Will close the Issue. Regards, |
Hi @gr2m could we also rotate this private key in timely manner? is the rotation possible ? Thanks in Advance. |
I don't think it's possible to programmatically change a GitHub App's private keys unfortunately. Repository secrets can be rotated though. |
Thank You again..! |
I am trying to checkout repo i github enterprise with this workflow, but i am getting the error as
Retrieving the default branch name Not Found
while i looked some other third party workflows, it worked.
eg: https://github.com/peter-murray/workflow-application-token-action
could you please help us here
Regards,
Atib
The text was updated successfully, but these errors were encountered: