-
Notifications
You must be signed in to change notification settings - Fork 438
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
Pushing to wrong project #554
Comments
I faced the same issue as well. In, my case, all updates go only to the latest project I have cloned. Haven't found a workaround yet |
Hello again. Since it's been a while and noone else seems to have this problem and I still have it I tried to dig a bit into clasps source.
Now I can confirm, that clasp thinks it is being called from In the folder |
As a workaround I changed the above mentioned function from (originally):
to
|
Working in 2 projects simultaneously seems not to work as intended.
I have two windows powershell terminals open at the same time.
Also two editors.
Lets say I work in projects A and B
Expected Behavior
Change A ->
PS C:\a>clasp push
-> project A updatedChange B ->
PS C:\b>clasp push
-> project B updatedActual Behavior
Change A ->
PS C:\a>clasp push
-> project A updatedChange B ->
PS C:\b>clasp push
->Manifest file has been updated...
-> yes -> project A has now content of project BSteps to Reproduce the Problem
Mentioned above.
Specifications
Could be the same as
#507
I just found out it was updating the wrong project because one of them is used as a library in the other.
The text was updated successfully, but these errors were encountered: