If you don’t, git will add modified files only, and not a new one. If you have added a brand new file and want git to include it in a stash - you will need to tick the checkbox. What’s important to note is the highlighted checkbox “ Include untracked files”. You may stash either all or just selected files and apply any existing stash. Here you set up default diff and merge tool commands. The screenshot below shows what it looks like through the GitExtensions UI. You can modify them manually in a plain text editor, but through the UI it feels a bit better. Git allows you to configure the environment (globally or per-repository) via config files. Explanations, therefore, of what this or that git command does are out of scope. Note: I assume you either use git on a daily basis (via a GUI interface or a console) or you are familiar with its concepts. I split the text into two self-descriptive parts: In this article I’ll walk you through the most frequent git actions and how I solve them. However, very soon I found myself more comfortable with using a hybrid approach - when I rely on GitExtensions in some scenarios (like commit or history inspection) and use a raw console for others. I thought the question of what git GUI tool to use was from the aforementioned category, because tools like SourceTree or GitKraken provide similar experience - at least from the first glance - and my choice fell on GitExtensions one day. The predefined choice just saves your time and brain capacity to make other important decisions. Those ones are not critical and often don’t make any difference, but can take a lot from you if you answer the same question every day. In my life I tend to make decisions that I wouldn’t like to revisit for a while (years-wise): what radio station to listen to, what electronics manufacturer to choose, or a service station to visit.

Why are git gui tools frowned upon