Skip to content

workflows permission missing #340

Description

@plastikfan

seeing this error in github actions:

[main 11ab90c] chore(gh-actions): apply auto-check edits
 36 files changed, 72 insertions(+), 610 deletions(-)
 delete mode 100644 .github/workflows/auto-check-workflow.yml
 delete mode 100644 scripts/automate-checklist.go
 delete mode 100644 scripts/automate-checklist.sh
 rename src/locale/default/{arcadia.active.en-GB.json => goo.active.en-GB.json} (100%)
 rename src/locale/deploy/{arcadia.active.en-US.json => goo.active.en-US.json} (100%)
 rename src/locale/out/en-US/{arcadia.translate.en-US.json => goo.translate.en-US.json} (100%)
 rename test/data/l10n/{test.arcadia.active.en-US.json => test.goo.active.en-US.json} (78%)
To https://github.com/snivilised/goo
 ! [remote rejected] main -> main (refusing to allow a GitHub App to create or update workflow `.github/workflows/ci-workflow.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/snivilised/goo'

When a repo is created from this template and the auto-check-workflow.yml is executed.

AI has suggested this as a solution:

To resolve the error refusing to allow a GitHub App to create or update workflow without 'workflows' permission, you must explicitly grant the workflows permission at the repository or organization level.

Fix the Error
Update Repository/Organization Settings:
Go to your repository or organization Settings → Actions → General.
Under Workflow permissions, select "Read and write permissions".
Click Save.
This enables the GITHUB_TOKEN to create or update workflow files like .github/workflows/ci-workflow.yml.
Alternative: Use a Personal Access Token (PAT): If you're using a PAT for authentication:
Go to Settings → Developer settings → Personal access tokens.
Regenerate or create a new token with the workflow scope.
Use this token in your git push or CI setup.
GitHub App Users: If using a GitHub App:
Go to the GitHub App settings.
Under Permissions, set Workflows to Read and write.
Reinstall the app to apply the updated permissions.
✅ Note: The actions: write permission in the workflow YAML is not sufficient for modifying workflow files. The workflows permission must be enabled in the repository/organization settings or granted via PAT/app.

Also see:

Metadata

Metadata

Assignees

Labels

choreNon source related, infrasture change

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions