Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider deprecating --clone options (add_plugin, ....) and moving to --repository #260

Open
stronk7 opened this issue Dec 6, 2023 · 0 comments

Comments

@stronk7
Copy link
Member

stronk7 commented Dec 6, 2023

Discussed @ #176 , we have at least 2 places where we support having:

  • A project that is the relative location of any github repo (owner/repo).
  • A repository option that is any arbitrary URL pointing to a git repo (github or elsewhere).

In some commands (add_plugin at very least), the "repository" option is named "clone" instead.

In order to make wording consistent, this issue is about:

  • In all the commands using any clone option, proceed to deprecate it (long deprecation) and create the repository option as new alternative.
  • Change all the docs around it.
  • Schedule the final removal of clone for next major release.

Ciao :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant