Node.js Bot Permissions
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
Description
Currently it looks like it has Write access, but the original idea was just for Read https://github.com/nodejs/docker-node/issues/670#issue-308668692
Is there a reason the Bot still needs Write access? It might change if https://github.com/nodejs/docker-node/issues/1008 goes forward, but right now it looks like it doesn't need it.
Right now it looks like it's only used by this repo, but with https://github.com/nodejs/admin/issues/471 maybe it will be re-used
Contributor guide
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 the linked docker-node issues 670 and 1008, then review nodejs/admin issue 471 to understand the bot's current and possible future use. Identify where the bot's repository permissions are configured; done means confirming whether Write access is required and reducing it to Read if it is not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100