configure ssh key for tagbot

[johnnychen94]

Here's the motivation:

One GitHub action could not trigger another GitHub action if only configured with token: ${{ secrets.GITHUB_TOKEN }}. This limitation means release/tag created by tagbot could trigger the docs CI.

@Evizero could you help set up an ssh key and corresponding github secrets for this? It should be ssh key with write permission in https://github.com/Evizero/Augmentor.jl/settings/keys (public, write permission) and secrets in https://github.com/Evizero/Augmentor.jl/settings/secrets/new (private)

The quick command to generate ssh key:

ssh-keygen -t rsa -b 4096 -C "stocker.christof@gmail.com" -f tagbot

then copy tagbot.pub as keys and tagbot as secrets (let's say with name "TagBot").

References:

• https://juliadocs.github.io/Documenter.jl/dev/man/hosting/#GitHub-Actions

[Evizero]

Ops. I missed or forgot this. Is this still relevant?

[johnnychen94]

Yes, I can update the CI configuration when this is added.

[Evizero]

Done. Let me know if i screwed it up :-)

[johnnychen94]

hard to tell unless there's a new release; I'll reopen if it doesn't work

[Evizero]

I just checked and I did this already. though the name is TagBot and not TAG_BOT like you mentioned in the mail. Will this work, or would you like me to change the name?

[Evizero]

actually the secret is TAGBOT

[Evizero]

actually hold that though, I think I might have screwed up the last part. I'll redo it now

[johnnychen94]

The one I configured in the CI is TAGBOT

Augmentor.jl/.github/workflows/TagBot.yml

Line 12 in 121b70d

ssh: ${{ secrets.TAGBOT }}

[Evizero]

try now. let me know if it doesnt work

[johnnychen94]

Oh, wait. I might not describe the need clearly in my previous mail. I was asking for adding a TAGBOT ssh key in UnicodePlots, too.

[Evizero]

done as well!