actions: write updates directly to redirectLinks.json to main

[flakey5]

Closes #66

[flakey5]

The deploy step is failing https://github.com/nodejs/release-cloudflare-worker/actions/runs/6933469355/job/18859682904, I assumed secrets.GH_USER_TOKEN would work automatically but that looks to not be the case. How can we go about adding it

[MoLow]

Is my help needed here? I can add a token if still needed

[ovflowd]

The deploy step is failing nodejs/release-cloudflare-worker/actions/runs/6933469355/job/18859682904, I assumed secrets.GH_USER_TOKEN would work automatically but that looks to not be the case. How can we go about adding it

You can simply just add the example mentioned there. But in general, these should be triggered on the "behalf" of an user. Adding the default token there might give an error that this Token has no access to this resource. Pretty much because GitHub Actions Tokens have access/scope only for that specific GitHub Workflow and Run.

[targos]

GH_USER_TOKEN is not the token generated by GitHub actions. If you want to use that one, it's GITHUB_TOKEN

[ovflowd]

GH_USER_TOKEN is not the token generated by GitHub actions. If you want to use that one, it's GITHUB_TOKEN

Right, yes. We need to pretty much then provide an user token.

[MoLow]

The workflow did not fail due to credentials, it failed because main is a protectd branch:

https://github.com/nodejs/release-cloudflare-worker/actions/runs/6964068075/job/18950729144#step:6:40

remote: error: GH006: Protected branch update failed for refs/heads/main.
remote: error: Changes must be made through a pull request. 3 of 3 required status checks are expected.

[ovflowd]

The workflow did not fail due to credentials, it failed because main is a protectd branch:

https://github.com/nodejs/release-cloudflare-worker/actions/runs/6964068075/job/18950729144#step:6:40

remote: error: GH006: Protected branch update failed for refs/heads/main.

remote: error: Changes must be made through a pull request. 3 of 3 required status checks are expected.

Huh? Interesting. We could bypass the rule for github actions (user I think?)

[MoLow]

yes, I am looking into this now

[targos]

I suggest to work with pull requests, even for automation. You can enable auto-merge in the repo settings and do something like this in a workflow (assuming token with enough permissions):

          # somehow create a branch and commit
          gh pr create --title "title" --body ""
          gh pr merge --auto --squash