Skip to content

CI: Update permissions#260

Closed
nourinmohd wants to merge 2 commits into
equinor:mainfrom
nourinmohd:update_permissions
Closed

CI: Update permissions#260
nourinmohd wants to merge 2 commits into
equinor:mainfrom
nourinmohd:update_permissions

Conversation

@nourinmohd

Copy link
Copy Markdown
Contributor

Resolves #259

Updated the permissions for the ci-fmudatamodels.yml.

Checklist

  • Tests added (if not, comment why)
  • Test coverage equal or up from main (run pytest with --cov=src/ --cov-report term-missing)
  • If not squash merging, every commit passes tests
  • Appropriate commit prefix and precise commit message used
  • All debug prints and unnecessary comments removed
  • Docstrings are correct and updated
  • Documentation is updated, if necessary
  • Latest main rebased/merged into branch
  • Added comments on this PR where appropriate to help reviewers
  • Moved issue status on project board
  • Checked the boxes in this checklist ✅

@nourinmohd
nourinmohd force-pushed the update_permissions branch from 3e971f1 to d945e83 Compare July 2, 2026 07:33
@GibranAlfa

Copy link
Copy Markdown
Collaborator

this won't work. workflow is not a valid github_token permission syntax (https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#permissions). the special case for this release is that we have a commit that change a file in .github folder (the pinning actions to hash), and github token doesn't have permission to do that. because this is rare, it's better to just do the schema release manually this time, and don't change any permission. regular schema release will work if it doesn't contain any commit that modify .github folder.

@GibranAlfa GibranAlfa closed this Jul 2, 2026
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

Successfully merging this pull request may close these issues.

Schema workflow fail due to permissions

3 participants