You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a private repo in which several packages are created, which are then to be published in a public repo. A token was set up in the Github account via “Settings->Developer settings->Personal access tokens (classic)”. This token was then added to the private repo via “Settings->Secrets and variables->Actions” as a repo secret with the name “PAT_TOKEN”.
The workflow of the private repo must check out the public repo, then the artifacts created in the private repo are downloaded to the checked out public repo and finally the downloaded artifacts are committed to the public repo.
Problem
The checkout fails, but the connection appears to be established successfully. Also, 2 retries are made until the process fails.
The error message “##[error]The process '/usr/bin/git' failed with exit code 1” is pretty trivial and doesn't say much, even though I have “GIT_TRACE” and “GIT_CURL_VERBOSE” enabled.
Situation
I have a private repo in which several packages are created, which are then to be published in a public repo. A token was set up in the Github account via “Settings->Developer settings->Personal access tokens (classic)”. This token was then added to the private repo via “Settings->Secrets and variables->Actions” as a repo secret with the name “PAT_TOKEN”.
The workflow of the private repo must check out the public repo, then the artifacts created in the private repo are downloaded to the checked out public repo and finally the downloaded artifacts are committed to the public repo.
Problem
The checkout fails, but the connection appears to be established successfully. Also, 2 retries are made until the process fails.
The error message “##[error]The process '/usr/bin/git' failed with exit code 1” is pretty trivial and doesn't say much, even though I have “GIT_TRACE” and “GIT_CURL_VERBOSE” enabled.
This is the release-snippet:
Additional infos:
Attached files:
4_release.txt
The text was updated successfully, but these errors were encountered: