Default `weasel clone` Behavior

Open
#6 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by reviewing the documented spacy project clone behavior and the current weasel clone command, including how the --repo argument is handled. Determine the intended command shape for a general git repository URL and define completion against the existing clone behavior and CLI documentation.

Written by the indexing model from the issue text.

Description

enhancement

Currently, spacy project clone takes a subdirectory of the projects repo as it's main argument. If weasel is going to be a general tool, we should probably change this behavior to make the primary argument a link to a git repository, rather than having that behavior behind the --repo argument.

Dominant language
Python
Stars
93
Forks
15
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from explosion/weasel

All issues in explosion/weasel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.