give internal users readonly access to mergebot objects
Open
Nobody has claimed this yet.
mergebot
- Dominant language
- Python
- Stars
- 159
- Forks
- 156
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 16
Description
Do they have any use for them? Dubious.
Is there any reason to keep them away? Not really, they they already have read access to some of the models (just not access to the menus / views), and access to the record data via the UI.
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
The issue does not name files, tests, or entry points. Start by locating the mergebot models and the existing internal-user access rules, then compare their model, menu, and view permissions. Done means the intended readonly access is defined and verified without granting write access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100