As discussed, we won't be implementing this feature. Since our config files are stored in a hidden file right in the path of the git repo, all config files are repo specific. That is, GiTA will only remember state per repo, which is desired behaviour.
As discussed, we won't be implementing this feature. Since our config files are stored in a hidden file right in the path of the git repo, all config files are repo specific. That is, GiTA will only remember state per repo, which is desired behaviour.