Skip to content

permissions #305

Description

@Aslemammad

i was debugging #300 and then i came to the conclusion that we might need contents write permission on the github app! which was not a good idea and was not even a solution!

we just reverted that access, so hopefully all good now!

but here i'm going to explain why we need certain permissions for the app!

Checks

image

So we can have this beautiful indicator:

image

Contents

We do not need writes on this! We just want to read a commit!
image

Pull Requests

image

We need to read and write comments! Write so you can have a comment, and Read so we do not duplicate.

Metadata

This is mandatory from github and I do not think we need it.

image

Commit Status

image

I do not think we need this since Checks already get the job done, let me try and see if we can remove it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions