Don't specify the password on the command line

[dseomn]

https://www.netmeister.org/blog/passing-passwords.html has a decent overview of the security issues with that.

Since this is interactive, getting curl to prompt for the password is probably the easiest alternative. From
https://curl.se/docs/manpage.html#-u

If you simply specify the username, curl prompts for a password.

I don't have an easy way to test the actual command in this doc, but the flag does seem to behave as documented at least:

$ curl --user [email protected] https://google.com Enter host password for user '[email protected]' 

Fixesgitgitgadget/gitgitgadget#1843

[dseomn]

Is this a bug in the workflow, or am I supposed to do something? I do have "allow edits by maintainers" checked.

Run git config user.name "dseomn" && [cmdline-no-secrets 10adce5] Convert Markdown to HTML 1 file changed, 1 insertion(+), 1 deletion(-) remote: Permission to dseomn/gitgitgadget.github.io.git denied to github-actions[bot]. fatal: unable to access 'https://github.com/dseomn/gitgitgadget.github.io/': The requested URL returned error: 403 Error: Process completed with exit code 128. 

[dscho]

Is this a bug in the workflow

This is something I wasn't sure whether it could work, see "Verify that the PR workflow succeeds to push updates even for PRs that originated from a fork" in #21 (comment).

[dscho]

Let me see what I can do about this.

[dscho]

There. 3rd times 3rd time is a charm:

For the record: I changed the PR build so that it no longer tries to push to the branch (unless the PR originates from the same repository) but instead publishes a Git bundle and describes how to pull from said bundle and then update the PR, which is what I did and therefore the PR build passed successfully.

Thank you @dseomn for your patience and for the contribution!