fix: fix tuistignore when local path are specified

[danieleformichelli]

Short description 📝

relative path (as the one we are specifying in Tuist own .tuistignore) were not matched correctly

Checklist ✅

• The code architecture and patterns are consistent with the rest of the codebase.
• The changes have been tested following the documented guidelines.
• The CHANGELOG.md has been updated to reflect the changes. In case of a breaking change, it's been flagged as such.
• In case the PR introduces changes that affect users, the documentation has been updated.

[adellibovi]

Since this is a more internal feature and we do not have expectations on the syntax of .tuistignore, I would rather change the content of the existing .tuistignore to be projects/tuist/fixtures/** instead of projects/tuist/fixtures rather than adding more logic. What do you think?

[danieleformichelli]

Not sure, I agree it's internal, but this might change in the future.
I would prefer to keep a syntax similar to the .gitignore to be as less surprising as possible and the additional logic is just a couple of lines.

[adellibovi]

I think if we start adding more behaviour/functionalities we may go into the direction where users would expect this to behave like .gitignore which actually have a lot more of features (like negating logic etc..). Functionality can always be added later, but removing them it is harder.
Said so, I would still personally prefer to adapt our .tuistignore instead of extending the functionality, anyway I will approve the PR 😃
It would be good to hear other opinions cc @fortmarek @pepibumur

[danieleformichelli]

@adellibovi I agree with your points, but in this case adding a folder would have no effect as the tuistignore works only on files, so it would be weird to have an entry which actually does nothing

[pepicrft]

CHANGELOG entry is missing but I'll update it in main to avoid delaying the merge further.