"unable to access" issue in multiple projects.

[tyler36]

Thank you for the creating this action.
I have several open-source projects that use this action to test against an upstream stable/head builds.

About a week ago, I started recieving email notifications of tests failing:

{
    "command": "git push origin HEAD",
    "exitCode": 128,
    "outputData": "",
    "errorData": "remote: Permission to tyler[3](https://github.com/tyler36/ddev-tinker/actions/runs/5162752635/jobs/9315661265#step:12:3)6/ddev-tinker.git denied to github-actions[bot].\nfatal: unable to access 'https://github.com/tyler36/ddev-tinker.git/': The requested URL returned error: [4](https://github.com/tyler36/ddev-tinker/actions/runs/5162752635/jobs/9315661265#step:12:4)03\n"
}

with:
    gh_token: ***
    commit_message: Automated commit by Keepalive Workflow to keep the repository active
    committer_username: gkr-bot
    committer_email: gkr-bot@tuta.io
    time_elapsed: 50
    auto_push: true
  env:
    NIGHTLY_DDEV_PR_URL: https://nightly.link/ddev/ddev/actions/runs/1720215802/ddev-linux-amd64.zip
    DDEV_GITHUB_TOKEN: ***
    HOMEBREW_NO_INSTALL_FROM_API: 1

Link to workflow.yml

[gautamkrishnar]

@tyler36 have you tried https://github.com/gautamkrishnar/keepalive-workflow#faqs-and-common-issues

[tyler36]

Thank you for the update.
I did check the link which highlights an issue while using protected branches but my project does not.

I added the "permission" line my workflow now which passes the test. This action reports "Nothing to do", because of the recent commit. I think I need to wait 60 days to find out if the dummy commit is working or not.

[rfay]

@tyler36 just change your time_elapsed in one or more of these repos to 1 or something and you'll know soon enough. Thanks!

[rfay]

@tyler36 I certainly wonder why tyler36/ddev-tinker#1 works, but doesn't seem to be needed on so many other repos. It could be personal vs org repos?

[gautamkrishnar]

@rfay it may work just fine for some older repos, The repos that are newly created may have read-only permission by default

[tyler36]

Confirmed working.

I set time_elapsed: 1 in my workflow and let it run for the last week. Everyday, dummy commits were added (as expected) and tests started passing again.

Thank you for the solution and discussion.

[rfay]

Thanks so much @tyler36 . Now we have to fix ddev-addon-template and eventually so many more. I'd sure like to know how Github changed default behavior of newer repos.

[gautamkrishnar]

https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/ this was the announcement they made

[rfay]

Ah thanks @gautamkrishnar - That article also makes it clear part of what's going on here.

Repositories owned by personal account: New repositories will have read-only token.

All of these that were having trouble were owned by personal account I think, and all the ones I maintain were owned by an org.