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

New feature of clasp revert clone! #990

Open
iRupam opened this issue Nov 18, 2023 · 2 comments
Open

New feature of clasp revert clone! #990

iRupam opened this issue Nov 18, 2023 · 2 comments

Comments

@iRupam
Copy link

iRupam commented Nov 18, 2023

(Note: Non-breaking issues are likely not to be prioritized. Please consider a PR in addition to your issue)

It's not an issue first of all. Just like to mention that it's a feature clasp should have.
I'd be happy to do the code for it too if I get some positive response regarding the feature.

Expected Behavior

We should be able to revert a bad clone. Some first time user might be cloning badly or simply don't want to clone.

Actual Behavior

There should exists some clasp clone revert kind of command similar to git revert.

Steps to Reproduce the Problem

  1. clasp clone "project id"

Specifications

  • Node version (node -v): v20.9.0
  • Version (clasp -v): 2.4.2
  • OS (Mac/Linux/Windows): Windows
@HoldYourWaffle
Copy link
Contributor

What would be the difference between clone revert and deleting the newly cloned folder?

@iRupam
Copy link
Author

iRupam commented Nov 18, 2023

I guess the effects of both are same, but would be nice if we can do from clasp command itself.

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

2 participants