Closed johnnychen94 closed 3 years ago
Ops. I missed or forgot this. Is this still relevant?
Yes, I can update the CI configuration when this is added.
Done. Let me know if i screwed it up :-)
hard to tell unless there's a new release; I'll reopen if it doesn't work
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?
actually the secret is TAGBOT
actually hold that though, I think I might have screwed up the last part. I'll redo it now
The one I configured in the CI is TAGBOT
try now. let me know if it doesnt work
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.
done as well!
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:
then copy
tagbot.pub
as keys andtagbot
as secrets (let's say with name "TagBot").References: