You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow up story of #757:
In PR #850 there were some remaining discussions left:
Missing .git folder in D:\projects\code-demo\settings. - can we prevent this warning since it is normal in this case?
Should we skip git pull on the code repo on ide update? Or otherwise at least add an option like ide update --skip-pull? I would actually suggest to skip the pull but render a warning if the git repo is not up-to-date but let the user in control of pulling and potential conflict resolution. We could also honor --force flag to trigger the update so ide -f update would still do the git pull but fail in case of merge conflicts.
The text was updated successfully, but these errors were encountered:
This is a follow up story of #757:
In PR #850 there were some remaining discussions left:
Missing .git folder in D:\projects\code-demo\settings.
- can we prevent this warning since it is normal in this case?git pull
on the code repo onide update
? Or otherwise at least add an option likeide update --skip-pull
? I would actually suggest to skip thepull
but render a warning if the git repo is not up-to-date but let the user in control of pulling and potential conflict resolution. We could also honor--force
flag to trigger the update soide -f update
would still do the git pull but fail in case of merge conflicts.The text was updated successfully, but these errors were encountered: