I really love the simplicity of Wappler and the way it allows us to do things in 1 application, but using GIT in Wappler for some things, and having to use a 3rd part GIT application for other functions defeats the purpose in my view. The way I use this often is to start with a clean GIT commit, then play around learning new things in current project and when I have figured it out I will roll back ALL uncommitted changes back to my known commit state. I am able to discard my changes in the source tree but had to select 1 file at a time if I select multiple it's still discarded only 1 at a. I guess in essence these new files are not in GIT yet so really don’t see why they shouldn’t be deleted when the user has selected them to be deleted? This behaviour is disorienting and confusing to an end user as without knowing the “how it is supposed to work” causes trust concerns as to what is rolled back and what is not, hence why I started using GitKraken for this function.įrom what I gather it is also different behaviour to the way GIT intended it to be used, at least when I look at how GitKraken does it, but by no means am I a GIT expert. On SourceTree for Mac, right click the files you want to discard (in the Files in the working tree list), and choose Reset. To verify the changes, execute the cat command as. The changes you made on the file have been saved successfully. For local branches, even though there is no automatic way, there is a way quicker than clicking through all unwanted branches. This will discard all working tree changes and move HEAD to the. Press CTRL+X keys to exit from the editor.
Then through GIT (refer to my screenshot in earlier post) on delete the routes file is rolled back, but the new file remains in place effectively orphaned until a new route is created? If your changes have not been pushed yet simply enter the command. Look at this situation in a nodejs project: lets say a new file is added, the routes file is updated to reflect the new route. 1 Answer Sorted by: 1 discard will only remove the local file changes that you have made to a specific file. I think the way it currently stands is confusing, and incorrect.
0 kommentar(er)
