support: Confusion about the content-directory

[wehrend]

Checklist

• I am using the latest version of this action.
• I have read the latest README and followed the instructions.
• I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your question

Hi there,
I recently got attracted to this project and could use a bit of help here... In particular I have some confusion about the content directory and its location in the file path - I want to have a complete filepath
like /home/runner/work/hugo/content - but gh pages get confused about the latter part and detects it as content/content.
Also I had some issue with the deploy key---

Relevant links

Public repository: https://github.com/wehrend/content
YAML config: (toml here): https://github.com/wehrend/content/blob/main/config.toml
YAML workflow: https://github.com/wehrend/content/blob/main/.github/workflows/deploy.yml

Relevant log output

Run peaceiris/actions-gh-pages@v4
with:
external_repository: wehrend/wehrend.github.io
publish_branch: main
publish_dir: ./wehrend.github.io
user_name: wehrend
user_email: [email protected]
allow_empty_commit: false
keep_files: false
force_orphan: false
enable_jekyll: false
disable_nojekyll: false
exclude_assets: .github
env:
HUGO_VERSION: 0.145.0
TZ: Europe/Berlin
[INFO] Usage https://github.com/peaceiris/actions-gh-pages#readme
Dump inputs
[INFO] : true
[INFO] PublishBranch: main
[INFO] PublishDir: ./wehrend.github.io
[INFO] DestinationDir:
[INFO] ExternalRepository: wehrend/wehrend.github.io
[INFO] AllowEmptyCommit: false
[INFO] KeepFiles: false
[INFO] ForceOrphan: false
[INFO] UserName: wehrend
[INFO] UserEmail: [email protected]
[INFO] CommitMessage:
[INFO] FullCommitMessage:
[INFO] TagName:
[INFO] TagMessage:
[INFO] EnableJekyll (DisableNoJekyll): false
[INFO] CNAME:
[INFO] ExcludeAssets .github

Setup auth token
Error: Action failed with "not found deploy key or tokens"

Additional context.

No response

[wehrend]

I figured out it would be easier, if I remove unneeded complexity and just reduce it to a one repositiory containing both form and functions, before that I had splitted blog itself and content, but the gh-pages apporaches eases it...