Support for /info/exclude

37 votes

GitKraken does not honor the exclusions in /info/exclude, which is a sort of per-clone .gitignore file that is itself not part of repository commits.

Some toolchains drop per-user preference or intermediate files among the source trees when building, and per-user .gitignore entries are not always appropriate to commit. For example, when such files are named with a per-user extension, each user needs a custom exclusion filter, which is not appropriate for a repo-wide .gitignore entry.

The solution is to put per-user exclusions in /info/exclude that are not part of the repo. Please support this mechanism.

Under consideration Suggested by: Nathan C. Sherman (18 Feb, '22) • Upvoted: 27 Mar • Comments: 2

Comments: 2

01 Sep, '22
Dave Mullen
Honestly, I'm kind of shocked that this wasn't implemented on day one. Git (and indeed other types) of repository are collaborative affairs usually centrally hosted, with people potentially working on their own branches / copies on their local machines.

But there is no mechanism for local users to ignore their own working files, configs, temporary files etc. without polluting the ".gitignore" file in the root of the repository that will (by design or by accident) become part of the shared repository.

Sadly, I already committed $60 to the "pro" version of this software, just to discover it doesn't have this basic mechanism in place.

I wish I could give this more than one upvote, or spread awareness somehow - only 3 upvotes in 6 months???
20 Dec, '22
Programmer
I really need this, my repo is a mess!