PS: Thanks you for your work on this extension btw, release 11.0. The main lesson here is that if you stage a file (thus adding a copy of that particular version to git), then go back and change the file you'll. This is less convenient though because there is no Compare current branch with command that I could use with F1, so I need to use the UI. Luckily for us GitKraken will show the new changes to the file in the 'Unstaged files' list (and it will show the earlier changes that you staged in the 'Staged files' list, which may be confusing). Fortunatly when I compare the 2 branches _gitlens_compare_tmp1 and _gitlens_compare_tmp2 under the Commits view I get No files changed under Ahead, so I can still compare my branches (see (2) in screenshot below). GitKraken is another one of the best GUI Git clients. In addition to creating files, you can also create folders by.
#GITKRAKEN FILE CHANGE CODE#
The code editor will open so you can jump right in and start working on your project.
To create a file, use the keyboard shortcut Cmd / Ctrl + P to open the Fuzzy Finder, type ‘ create file ’, and then type the name of your file. I often use this functionality when I rewrite my branches history to check that I keep the same files on the original and the rewritten branch. Git config file setup To set up your Git config file, open a command line for the distribution. Now you can create and delete files in GitKraken. If you click on any file under these lists, the diff view opens but reports no changes. Adding the LICENSE file will initially be an untracked change (it’s a new file), while the other changes that edit existing files will be tracked. In the Search & Compare view you should see 5 files changes reported under Behind and Ahead (See (1) in screenshot below). I’ll be making these edits in three parts: (1) adding a LICENSE file, (2) adding a copyright notice to our main.cpp file, and (3) adding an abbreviated copyright notice to the other source files.