stackblitz-labs / stackblitz-labs/pkg.pr.new
permissions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
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
So we can have this beautiful indicator:
Contents
We do not need writes on this! We just want to read a commit!
Pull Requests
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.
Commit Status
I do not think we need this since Checks already get the job done, let me try and see if we can remove it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #300 and reviewing the GitHub App permission configuration for Checks, Contents, Pull Requests, Metadata, and Commit Status. Confirm which permissions are required for reading commits, displaying checks, and reading or writing comments, then verify that unnecessary access can be removed without losing those behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, security
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100