The Welkin Suite Forum

new project from source deleted my entire GIT repo



new project from source deleted my entire GIT repo

GIT
  • Please log in to reply

#1
mac version welkinsuite

ron

    Posted 24 Jul 2019 and edited 30 Jul 2019

    I installed the Welkin suite, opened it, clicked salesforce project from source, and I indicated to the tool that I have a GIT repo.  ( use git for version control )

    The Welkin suite proceeded to delete my GIT REPO including all my stashes, private branches, etc...

    The repo is not in the trash either ( on mac), the suite then reported a problem and would not continue.


    This is a blocker for me to proceed with an evaluation, and now my sources are gone, where are my source directories?



    11 replies to this topic

    #2

    ihor.zhabolenko

      Posted 25 Jul 2019

      Hello Ron.

       
      This really does sound frustrating, thank you for contacting us.
       
      May I please ask you to tell me if you selected "Create a project file close to sources" or "copy sources to project folder"
      Window.jpg
      (screen with this setting)

      If you selected "a creation of a new project in the same folder" -this is a reason for the issue. The project was created according to selected settings.
       
      To be honest, we haven't been faced with this case previously and had no issues on this.
      We will add some additional notification to avoid the issue in the future.
       
      If you selected another set during the project creation - "copy sources to project folder", in this case, TWS has no write access to your local repository folder.
       
      Looking forward to hearing from you.

      Regards, 
      Ihor

      TWS Team


      #3

      ron

        Posted 25 Jul 2019

        I believe I selected to create a project near my sources.  I feel strongly that no tool should delete a folder which has a .git repro already in place.

        Even if it is my mistake, the cost to recover is too high.



        #4

        ihor.zhabolenko

          Posted 26 Jul 2019

          Thank you, Ron, for your reply.

          We will add some warning message there.

          Again, I am very sorry for the inconvenience.

          Please contact customer support for any further concerns you might have – we are always very happy to help.


          Regards,

          Ihor



          TWS Team


          #5

          marc.behr

            Posted 29 Jul 2019

            Ihor,

            Is there any reason why we can't have an option to allow us to simply add the needed TWS files to an existing directory? In other words, I already have a git controlled directory on my system that I was using something like Visual Code to work with. Now I want to switch to (or try) using TWS for the same project. What I want is an option that says "Add TWS to existing directory" that will leave all of the files in that directory as is, but then just add whatever files TWS needs. Your init code should leave things in the existing directory alone.

            Marc



            #6

            ihor.zhabolenko

              Posted 29 Jul 2019

              ron, on 25 Jul 2019 - 06:48 PM, said:

              I believe I selected to create a project near my sources.  I feel strongly that no tool should delete a folder which has a .git repro already in place.

              Even if it is my mistake, the cost to recover is too high.


              Hi Ron.

              We are looking into the issue you have contacted us with, unfortunately, it has not been reproduced so far, the scenario mentioned in our previous letter worked as intended during the tests.

              Could you please share with us some more details on the process you had when the issue occurred, perhaps some screens or steps? Was the project created to the same folder where the sources were or have you chosen option to copy sources to the new project folder at that time point?

              We really want to address the issue and would be glad to help you


              Regards,

              Ihor


              TWS Team


              Post deleted by author.

              #8

              ihor.zhabolenko

                Posted 29 Jul 2019

                marc.behr, on 29 Jul 2019 - 11:53 AM, said:

                Ihor,

                Is there any reason why we can't have an option to allow us to simply add the needed TWS files to an existing directory? In other words, I already have a git controlled directory on my system that I was using something like Visual Code to work with. Now I want to switch to (or try) using TWS for the same project. What I want is an option that says "Add TWS to existing directory" that will leave all of the files in that directory as is, but then just add whatever files TWS needs. Your init code should leave things in the existing directory alone.

                Marc

                 Hello Marc.

                Thank you for your question.

                You could add the needed TWS files to an existing directory. After this, you just need to use the "Refresh project according to sources" functionality to reflect source changes in the project. 


                I hope it should help to resolve your case.


                Please let me know if this would help you.


                Regards,

                Ihor


                TWS Team


                #9

                marc.behr

                  Posted 29 Jul 2019

                  ihor.zhabolenko, on 29 Jul 2019 - 01:28 PM, said:
                  marc.behr, on 29 Jul 2019 - 11:53 AM, said:

                  Ihor,

                  Is there any reason why we can't have an option to allow us to simply add the needed TWS files to an existing directory? In other words, I already have a git controlled directory on my system that I was using something like Visual Code to work with. Now I want to switch to (or try) using TWS for the same project. What I want is an option that says "Add TWS to existing directory" that will leave all of the files in that directory as is, but then just add whatever files TWS needs. Your init code should leave things in the existing directory alone.

                  Marc

                   Hello Marc.

                  Thank you for your question.

                  You could add the needed TWS files to an existing directory. After this, you just need to use the "Refresh project according to sources" functionality to reflect source changes in the project. 


                  I hope it should help to resolve your case.


                  Please let me know if this would help you.


                  Regards,

                  Ihor

                  Ihor, 

                  How exactly do I "add the needed TWS files to an existing directory"? What are the files that TWS needs?


                  Scenario:

                  I have a project in a git reposititory that I have been using Visual Code for develeopment and now I want to test using TWS. So on my local system, I have the following directory structure (as an example): 

                  ~/Projects/my_project/objects/
                  ~/Projects/my_project/workflows/
                  ~/Projects/my_project/classes/
                  ~/Projects/my_project/aura/
                  [...]

                  Now I want to test TWS to compare it to how VC works, while maintaining the git layout that already exists. Which option do I select to see the data in TWS correctly, without moving or altering the existing data?

                  As I understand it, if I select 'Create project newar my sources', TWS will copy things from where they are into new directories, thus breaking git.


                  Am I missing an option or exactly what steps should I take to be able to test TWS in this scenario? (note, I too am on a Mac).


                  Thanks!



                  #10

                  ron

                    Posted 29 Jul 2019

                    I understand you are not able to repro the issue.  I am still working on recovering and do not have any

                    screenshots or better recollection of the exact sequence, sorry.   I guess you would look thru your code for unlink() on a directory. 

                    The only hint that I can offer is that I named my welkin project the exact name as my repo directory.



                    #11

                    ihor.zhabolenko

                      Posted 30 Jul 2019

                      ron, on 29 Jul 2019 - 04:47 PM, said:

                      I understand you are not able to repro the issue.  I am still working on recovering and do not have any

                      screenshots or better recollection of the exact sequence, sorry.   I guess you would look thru your code for unlink() on a directory. 

                      The only hint that I can offer is that I named my welkin project the exact name as my repo directory.


                      Hi Ron,

                      Thank you for your answer.

                      We have also checked the flow with the same name for both - project and repository and still got everything working as expected. Unfortunately, we can neither investigate further this question due to a lack of more details nor confirm if the issue is welkin-related at all.

                      Thank you for getting in touch with us and finding the time to communicate and describe your situation


                      Regards,

                      Ihor


                      TWS Team


                      #12

                      ihor.zhabolenko

                        Posted 30 Jul 2019 and edited 30 Jul 2019

                        marc.behr, on 29 Jul 2019 - 01:50 PM, said:
                        ihor.zhabolenko, on 29 Jul 2019 - 01:28 PM, said:
                        marc.behr, on 29 Jul 2019 - 11:53 AM, said:

                        Ihor,

                        Is there any reason why we can't have an option to allow us to simply add the needed TWS files to an existing directory? In other words, I already have a git controlled directory on my system that I was using something like Visual Code to work with. Now I want to switch to (or try) using TWS for the same project. What I want is an option that says "Add TWS to existing directory" that will leave all of the files in that directory as is, but then just add whatever files TWS needs. Your init code should leave things in the existing directory alone.

                        Marc

                         Hello Marc.

                        Thank you for your question.

                        You could add the needed TWS files to an existing directory. After this, you just need to use the "Refresh project according to sources" functionality to reflect source changes in the project. 


                        I hope it should help to resolve your case.


                        Please let me know if this would help you.


                        Regards,

                        Ihor

                        Ihor, 

                        How exactly do I "add the needed TWS files to an existing directory"? What are the files that TWS needs?


                        Scenario:

                        I have a project in a git reposititory that I have been using Visual Code for develeopment and now I want to test using TWS. So on my local system, I have the following directory structure (as an example): 

                        ~/Projects/my_project/objects/~/Projects/my_project/workflows/~/Projects/my_project/classes/~/Projects/my_project/aura/[...]

                        Now I want to test TWS to compare it to how VC works, while maintaining the git layout that already exists. Which option do I select to see the data in TWS correctly, without moving or altering the existing data?

                        As I understand it, if I select 'Create project newar my sources', TWS will copy things from where they are into new directories, thus breaking git.


                        Am I missing an option or exactly what steps should I take to be able to test TWS in this scenario? (note, I too am on a Mac).


                        Thanks!


                        Hi Mark


                        As you might see from our answers above, our team have not been getting any issues related to the git directory while the projects were set "close to sources" these days.
                        Next articles show how new projects can be easily and successfully created within this option:


                        https://welkinsuite.com/blog/creating-salesforce-project-from-git-sources/


                        https://welkinsuite.com/blog/3-ways-to-store-salesforce-project-in-git/


                        We would also recommend you to pay attention to any git-related messages, in case you see any, thrown by 3rd party applications which you might have installed on your machine. And of course, to feel less pressure while you are trying the new flow and to protect your data in any case, "My_project" folder can be just backed up in advance, just to be sure.


                        Please, do not hesitate to ask any following question and let us know how it worked for you!

                        Regards,

                        Ihor


                        TWS Team





                        Boost Your Productivity. Get Started Today

                        Try Free Trial