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

fix(ci): setup permissions set for github token #291

Closed

Conversation

Vacxe
Copy link
Member

@Vacxe Vacxe commented Oct 25, 2024

Interesting workaround permissions setup:

    permissions:
      actions: write
      attestations: write
      checks: write
      contents: write
      deployments: write
      id-token: write
      issues: write
      discussions: write
      packages: write
      pages: write
      pull-requests: write
      repository-projects: write
      security-events: write
      statuses: write

Result

Could not add a commit status, the GitHub token for Danger does not have access rights.
If the build fails, then danger will use a failing exit code.

However

permissions: write-all

Working as expected.


From private fork comment message not posted, but from repo branch all work as expected

@Vacxe Vacxe force-pushed the fix-ci-permissions-for-default-token branch 4 times, most recently from 76e7d8a to c9cd353 Compare October 25, 2024 16:48
@Vacxe Vacxe force-pushed the fix-ci-permissions-for-default-token branch from c9cd353 to 839d81c Compare October 25, 2024 16:53
@Vacxe Vacxe closed this Oct 25, 2024
@Vacxe Vacxe reopened this Oct 25, 2024
@Vacxe Vacxe closed this Oct 25, 2024
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.

1 participant