Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tagbot fails #35

Open
pwochner opened this issue Dec 16, 2024 · 0 comments
Open

Tagbot fails #35

pwochner opened this issue Dec 16, 2024 · 0 comments

Comments

@pwochner
Copy link
Contributor

pwochner commented Dec 16, 2024

Problem

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant