Fail on building (wrong wiki URL) :)

[201flaviosilva]

Hey there,

I'm getting this error:

Run Andrew-Chen-Wang/github-wiki-action@v3
/usr/bin/docker run --name dd1ff46e74abf427fa3a3f2b4969042dd_5453a0 --label 08450d --workdir /github/workspace --rm -e WIKI_DIR -e GH_TOKEN -e GH_MAIL -e GH_NAME -e EXCLUDED_FILES -e INPUT_WIKI_DIR -e INPUT_GH_TOKEN -e INPUT_GH_MAIL -e INPUT_GH_NAME -e INPUT_REPO -e INPUT_WIKI_PUSH_MESSAGE -e INPUT_EXCLUDED_FILES -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/HillClimbing.js/HillClimbing.js":"/github/workspace" 08450d:d1ff46e74abf427fa3a3f2b4969042dd
REPO ENV is missing. Using the current one.
Cloning into 'temp_wiki_622accf3f238ac9d08144d8eca3d57e616fbde65'...
Cloning wiki git...
Message:
try fix wiki build
Copying files to Wiki
sending incremental file list
./
Home.md

sent 170 bytes  received 38 bytes  416.00 bytes/sec
total size is 56  speedup is 0.27
rm: can't remove 'temp_wiki_622accf3f238ac9d08[14](https://github.com/201flaviosilva/HillClimbing.js/runs/6472581198?check_suite_focus=true#step:4:14)4d8eca3d57e616fbde65/_ignore': No such file or directory
Pushing to Wiki
[master 4df3484] try fix wiki build
 1 file changed, 2 insertions(+)
remote: Permission to [20](https://github.com/201flaviosilva/HillClimbing.js/runs/6472581198?check_suite_focus=true#step:4:20)1flaviosilva/HillClimbing.js.wiki.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/201flaviosilva/HillClimbing.js.wiki.git/': The requested URL returned error: 403

For what I understood this is trying to find a GitHub wiki in https://github.com/201flaviosilva/HillClimbing.js.wiki/ but my GitHub wiki is in the https://github.com/201flaviosilva/HillClimbing.js/wiki , any help ? 😅

• Repository: https://github.com/201flaviosilva/HillClimbing.js
• Error: https://github.com/201flaviosilva/HillClimbing.js/runs/6472581198?check_suite_focus=true
• Wiki: https://github.com/201flaviosilva/HillClimbing.js/wiki
• DeployWiki.yml: https://github.com/201flaviosilva/HillClimbing.js/blob/main/.github/workflows/DeployWiki.yml

(Sorry if it was confusing)

[Andrew-Chen-Wang]

https://github.com/201flaviosilva/HillClimbing.js.wiki/ is the actual git repository uri.

Two things could be happening:

• You originally had this in private, which I doubt since it's an NPM package. But if you did, you would've needed a GitHub PAT
• More likely, the email you used is not the one associated with your GitHub account, but I could be wrong.

Otherwise, it might be a bug? The new version was submitted by a user that I saw had this working fine, so not entirely sure what else could be happening.

[rcdailey]

@201flaviosilva I think I see the issue. Look at the logs here:

GITHUB_TOKEN Permissions
  Contents: read
  Metadata: read

You need to give GITHUB_TOKEN write permissions, I think. Read more here.

In my personal project, I use a personal access token (which already has permission to push to my repo) and it works:

env:
  WIKI_DIR: wiki/
  GH_TOKEN: ${{ secrets.PAT }}
  GH_MAIL: ${{ secrets.EMAIL }}
  GH_NAME: ${{ github.repository_owner }}
  EXCLUDED_FILES: "*.json"

[Andrew-Chen-Wang]

Previously, the GITHUB_TOKEN should be working fine. Reading this, https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token @201flaviosilva can you try adding the additional permissions using the permissions label? If that doesn't work, we may need to revise the README and say that GITHUB_TOKEN doesn't work.

I'll take a look at the community and see whether GITHUB_TOKEN works for anyone using v3.

Thanks for taking a look at this @rcdailey greatly appreciated!

[rcdailey]

The only functional difference I can see is that we use $GH_NAME:[email protected] instead of just [email protected] in the clone URL. Push used both before. But I'm fairly confident only one should be used. I'm not able to find official documentation from Github that shows which one is proper, but based on my searching (see references below), the latter seems to be the most commonly used format. Should we test with just the GH_TOKEN in the clone URL and see if that makes a difference?

At the end of the day, I don't see how GITHUB_TOKEN should work anyway without being in permissive mode. There's quite simply no documentation that I've found that shows it should work in restrictive mode. I agree sampling the community and further auditing the documentation is a good thing to do, though.

References: 1, 2, 3

[201flaviosilva]

Sorry for only replying now, I was on my way home.

But finally the problem is solved :)

It was really a permissions issue. Thank you very much for the tool and the excellent support, you saved my life 😁

(And sorry for wasting your time with this silly problem 😅)

[Andrew-Chen-Wang]

No I definitely learned something today as well :) Thanks for asking!