RemoteCollection: no trivial way to detect if a remote already exists
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
Description
I would like to think that a try/except for ValueError on create() would be sufficient, but I see no guarantee that the only reason a ValueError might be thrown on create() is if the remote already exists. So it feels like I need to check if the remote exists by hand before trying to create it?
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 locating the RemoteCollection API and its create() entry point. Review how create() reports ValueError and whether an existence check is already exposed; done means callers have a documented, reliable way to determine whether a remote exists without guessing why create() failed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100