You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tagbot fails with the following error when trying to push to HerbCore:
To https://github.com/Herb-AI/HerbCore.jl
! [remote rejected] v0.3.3 -> v0.3.3 (refusing to allow a GitHub App to create or update workflow `.github/workflows/TagBot.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/Herb-AI/HerbCore.jl'
Error: TagBot experienced an unexpected internal failure
What I tried so far (without success)
We had problems with TagBot before, see here.
Neither of the previous "solutions" are relevant here. The repo had neither a DOCUMENTER_TOKEN IN Settings -> Security -> Secrets and variables -> Actions, nor any ruleset in Settings -> Code and automation -> Rules -> Rulesets.
Removed ssh: ${{ secrets.DOCUMENTER_KEY }} from TagBot.yaml since there was no DOCUMENTER_KEY in Secrets and variables anyway.
Checked that HerbCore Settings -> Code and automation -> Actions -> General are as described in TagBot set up.
Comparison to HerbGrammar.jl and HerbConstraint.jl, where TagBot recently ran successfully.
In both repositories:
TagBot.yaml still has ssh: ${{ secrets.DOCUMENTER_KEY }}.
But neither deploy keys nor repository secret are set, as would be required for using SSH deploy keys with TagBot. So I don't think that the ssh in the yaml file should make a difference.
Logs: Set up job looks the same. No difference between the ones that failed and succeeded.
The text was updated successfully, but these errors were encountered:
Problem
Tagbot fails with the following error when trying to push to HerbCore:
What I tried so far (without success)
Neither of the previous "solutions" are relevant here. The repo had neither a
DOCUMENTER_TOKEN
IN Settings -> Security -> Secrets and variables -> Actions, nor any ruleset in Settings -> Code and automation -> Rules -> Rulesets.ssh: ${{ secrets.DOCUMENTER_KEY }}
fromTagBot.yaml
since there was noDOCUMENTER_KEY
in Secrets and variables anyway.TagBot
recently ran successfully.In both repositories:
TagBot.yaml
still hasssh: ${{ secrets.DOCUMENTER_KEY }}
.The text was updated successfully, but these errors were encountered: