For 19.2 we will try to be more selective here when to require a clean working tree and when not. git filter-branch -f -index-filter git rm -rf -cached -ignore-unmatch FOLDERNAME. Now, combining both, you will run into the problem that SmartGit will ask you to auto-stash before performing a history-related operation, but then will not actually stash the untracked files and hence the operation fails because the working tree is not clean.Ī quick solution to the problem is to enable stashing of untracked files in the Preferences, section Commands, Stash. CD to your local working folder and run the following command. Proposal Add a feature that allows the user to provide the files / directories he wants to exclude from the mirroring. But certain files should not get updated in the repositories like the README.md for example. We want them to update automatically as the framework gets improved. You can also view and manage pull requests for your open source projects from SmartGit. You can then clone, fork, commit or push to your remote repositories from inside SmartGit. That’s behavior already present in version 18.2. All our repositories are forks from that framework. Using OAuth, you can connect SmartGit with your accounts in Github, GitLab, Bitbucket, or Stash and access the remote repositories there. However there is some problem in SmartGit 19.1’s logic though: SmartGit is not stashing untracked files by default, because certain SmartGit users think that SmartGit must not touch untracked files at all.
![smartgit ignore folder smartgit ignore folder](https://www.syntevo.com/assets/images/products/smartgit/whats-new/v18-1/add-worktree-2e6e29a3.png)
Hence, we require a clean working tree in general. It’s not clear whether all of these operations in combination with the interactive rebase can cope perfectly with untracked files for different scenarios (e.g. This is especially true for history-related operations, for which SmartGit is now using Git’s interactive rebase feature. In general, SmartGit considers untracked files more important than Git in various places (if not important, why not ignore them?).
![smartgit ignore folder smartgit ignore folder](https://www.syntevo.com/assets/images/products/smartgit/whats-new/v18-1/ignore-d4ba856e.png)
![smartgit ignore folder smartgit ignore folder](https://i.stack.imgur.com/ib5Sw.jpg)
Most of the time we should use this command to update the committed message without touching the file. A couple of users have complained about changes to the auto-stashing behavior in version 19.1 (compared to 18.2): for various history-related operations (like reordering, squashing of splitting commits), SmartGit 19.1 is now requiring a clean working tree where SmartGit 18.2 did not and also Git command line does not. Let’s say if we want to undo the commit but keep all files staged then we should use the following command.