![]() In any case if it is believed that the way it currently behaves in Wappler is correct then I think we are better of to remove the rollback uncommitted files function altogether as in my view partial rollbacks are worse than no rollback. 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. ![]() To unstage a file again, just check the checkbox next to the staged file and the file will be back in unstaged mode. To delete unstaged files, you can do it from the command line using. Note that this will also change the URL of the repository so anybody with access to this repo will need to update the remote url. 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. 1 Click on commit 2 Select all by pressing CMD+Athat you want to delete or discard 3 Right clickon the selected uncommitted files that you want to delete 4 Select Removefrom the drop-down list. Git SourceTree How to Reset or Revert code changes. Uncommited or even staged changes will be lost when you run the reset command If you want to keep those you can. If youre using Bitbucket Cloud for example, you can go to your repository, click Settings and update the name. If I commit the files I want to keep and click 'Discard' to rid my branch of the other(s), and then select the file(s) to discard, about half of the time ST claims I havent selected a file (bad). 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? ST wont let me change branches if there are uncommitted/unstashed file changes (good). This obliterates not only the uncommitted changes. 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. Move the current branch tip backward to and reset both the staging area and the working directory to match. 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? 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. ![]() ![]() I think the way it currently stands is confusing, and incorrect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |