-
Notifications
You must be signed in to change notification settings - Fork 122
Fails with git error (could not read Password) #34
Comments
Can you try using the latest version ( |
Thanks for the quick answer. I'll re-try via the personal access token in a few days. I don't think the git push is password based. Instead of committing as a certain user, the commits are coming from "GitHub actions". I guess that's also the reason they work reliably with GITHUB-TOKEN instead of a personal token. This might be also preferred in a organizational environment, where you usually don't want to use a personal access token in build. |
I would love to be able to just rely on the |
Judging from the fact that the following code successfully commits to
I sadly miss the experience with github actions to see how it works or provide further details. If there is something I can test, please let me know! |
It was still failing with 2.0.3 (with the same error message). https://github.com/JabRef/www.jabref.org/runs/702023453 |
Glad it works as expected 😄 |
Hey! maybe you could look at this on how to push to github pages with |
Using the action, we got the following error during the run:
(see https://github.com/JabRef/www.jabref.org/runs/683214840?check_suite_focus=true with config https://github.com/JabRef/www.jabref.org/blob/ddb2c53748ba0e89ab085aa593ad339fffc915c2/.github/workflows/publish.yml)
I guess the problem is the git user config. Maybe it works if one uses the following config taken from the github-push action:
I also want to remark that the repo url is different in the github-push action:
https://github.com/ad-m/github-push-action/blob/master/start.sh#L27
vs
https://github.com/helaili/jekyll-action/blob/master/entrypoint.sh#L49
but I don't have enough experience to judge which version is better.
The text was updated successfully, but these errors were encountered: