Upstream mousebender.simple for a simple repository API submodule?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 751
- Forks
- 324
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 3
Description
Basically bring https://github.com/brettcannon/mousebender/blob/main/mousebender/simple.py here. @d3r3kk and myself would do the work.
If people like this idea we can discuss if the API works for people, what the submodule should be named (index? simple? simpleindex? repoapi? repo?), etc.
We do want to do https://github.com/brettcannon/mousebender/issues/48 which has a PR at https://github.com/brettcannon/mousebender/pull/51 that's still being discussed, but I figured we don't really need to wait for that in order to upstream the rest of it now.
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 mousebender/simple.py and the linked mousebender issue 48 and pull request 51. Determine whether the API is ready to upstream and settle the submodule name among the options listed; done means an agreed repository API is brought into this project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100