Enable website publishing in CI

[danicheg]

No description provided.

[danicheg]

I lack access to this part of the repo's settings in Github, so I need some assistance setting this token up https://scalameta.org/mdoc/docs/docusaurus.html#deploy-key Maybe @SethTisue can do that?

[SethTisue]

I followed the steps, accurately I hope :-)

[SethTisue]

https://github.com/scalacenter/scalac-profiling/actions/runs/7441157666/job/20242939961 was automatically triggered when I merged this, but it seems to have failed for reasons I don't understand. @danicheg any insight?

[danicheg]

@SethTisue Thank you!
In the logs, I see this

Cloning into 'scalac-profiling-gh-pages'...
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Have you enabled the Allow write access in the settings as specified in docs?
Also, maybe env var is something different from GITHUB_DEPLOY_KEY?
As yet another idea, this might be related to this paragraph from docs — It's important to use an empty passphrase so that the CI can install the key.

[SethTisue]

I did use an empty passphrase.

You mean GIT_DEPLOY_KEY, not GITHUB_DEPLOY_KEY. It appears correct to me at https://github.com/scalacenter/scalac-profiling/settings/secrets/actions

Have you enabled the Allow write access in the settings as specified in docs?

Yes, at https://github.com/scalacenter/scalac-profiling/settings/keys I see it says "Read/write"

Maybe the clone is failing because the gh-pages branch doesn't exist yet? Maybe you need to create it first?

[danicheg]

Maybe the clone is failing because the gh-pages branch doesn't exist yet?

(It's there already)

[danicheg]

You mean GIT_DEPLOY_KEY, not GITHUB_DEPLOY_KEY. It appears correct to me at https://github.com/scalacenter/scalac-profiling/settings/secrets/actions

I cannot visit that page. But just to confirm, you've set up the GIT_DEPLOY_KEY env var, right? If so it might be the reason, because in CI, I expected this one ${{ secrets.GITHUB_DEPLOY_KEY }}

[SethTisue]

Yes, that must be the problem. I used GIT_DEPLOY_KEY because that's what https://scalameta.org/mdoc/docs/docusaurus.html#deploy-key suggested.

Hopefully #77 will fix it