[improve][ci] change token name to GITHUB_TOKEN

[labuladong]

Fixes #909

Modifications

Change token to GITHUB_TOKEN.

After changing, the pulsar bot works fine. Example here:

https://github.com/labuladong/pulsar-client-go/actions/runs/3681253024/jobs/6227745474#step:4:27

[tisonkun]

Thank you! Although I suppose we can omit this env var at all and let the action read from preset ENV. But since it works and does no harm, let's move forward with this patch first.

[tisonkun]

A possible issue is that this default token may not have the write permission required and thus fail to write comment/update status on demand. You can check it (it may work differently from you personal fork and in the upstream) or we just give it a try.

[labuladong]

A possible issue is that this default token may not have the write permission required.

I found the bot in the pulsar repo also uses another token:

So maybe you are right. I guess the default token doesn't have permission to restart the CI task.

[labuladong]

Yes, the behavior in the upstream repo may be different from my fork. So this pr may not work. Do you have any ideas to fix the bug about the CI bot? @tisonkun

[labuladong]

Some information about GITHUB_TOKEN:

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

[tisonkun]

This change doesn't make the case worse. Let's give it a try.

If it still won't work, we can find other approach or just remove the workflow since we actually live well without this functionality always.

[tisonkun]

rerun-failed-jobs for 'CI'. Follow progress at https://github.com/apache/pulsar-client-go/actions/runs/2812684476
{
  "message": "Unable to retry this workflow run because it was created over a month ago",
  "documentation_url": "https://docs.github.com/rest/reference/actions#re-run-workflow-failed-jobs"
}
Failed.

https://github.com/apache/pulsar-client-go/actions/runs/4698390864/jobs/8330614311

It seems default token doesn't have enough permission to trigger rerun. Although we can file an INFRA ticket to add one, but IIRC INFRA will reject configure personal access token as we do before - we may be an actual bot account.

I'm OK to leave it as is or delete the workflow file since we can actually live well without this functionality.