Repository discovery doesn't have the right permission
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 368
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
With https://github.com/rust-lang/team/pull/2630 we should create PRs when a new repository is added manually to one of the rust-lang organizations.
However, this PR uses the GitHub app of the dry run to open the PR. That github app lacks permissions to open PRs.
Should we create a new GitHub App with write permission on pull request and contents?
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 reviewing pull request 2630 and the dry-run GitHub App used to open repository-discovery PRs. Confirm which permissions are missing for pull requests and repository contents, then verify that the selected app configuration can create PRs when a repository is added manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- authorization, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100