{"thread":{"id":"60957","subject":"Re: Why does the includeif woks how it does?","startedAt":"2024-02-20T06:54:45Z","lastAt":"2024-02-20T06:54:45Z","messageCount":1,"participants":["Dominik von Haller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"488962","messageId":"FR2P281MB16867E5D8C722A787F6CFEDABA502@FR2P281MB1686.DEUP281.PROD.OUTLOOK.COM","threadId":"60957","inReplyTo":null,"subject":"Re: Why does the includeif woks how it does?","fromName":"Dominik von Haller","fromEmail":"vonhaller@fastec.de","sentAt":"2024-02-20T06:54:42Z","receivedAt":"2024-02-20T06:54:45Z","isPatch":false,"sender":{"key":"vonhaller@fastec.de","avatar":null},"body":"Thanks, you all for your insights. <3\n\n\nSo to summarize, it was implemented through a gitdir because of possible confusions with the working directory. And there is no other implementation because the use case is not there.\n\nFor the new implementation I would always use the working directory. If set with git -C than use that. Should also not be a Problem because the working directory it is set internally anyway.\n\n\nAs far as the possible implementation of this goes, I would prefer an includeif with an extra option dir instead of gitdir. This would prevent confusion between includewhere and includeif.\n\nThe mentioned Problems seem to be easily figured out.\nEvery includeif == true will get included. Every more specific path will overwrite properties if set before. Gitdir is more specific than just dir.\nSomewhat like that I would say is very intuitive.\n\nAnother possible approach which I would also say is logical is a top-down approach. Every Includeif would be executed from top to bottom. Every true includeif will be included and as before would overwrite properties if necessary. \n\n\nBest regards\nDominik von Haller \n"}]}