Closed hzierer closed 5 months ago
Hi @hzierer, is this really a dashboard issue? or more general quality checks tool related? can you provide an example of a monorepo for which it is an issue?
AFAIK, the warning for TRG 1.02 regarding a missing INSTALL.md is intended. This was meant to remind people, that it could be a good idea. But I also see, that it leads to confusion, especially in the monorepo case @hzierer mentioned.
I saw repos, where there have been INSTALL.md
files, but in /frontend
and /backend
directories. In this case the reminder is odd, since they actually have the file. Just in a different place
For TRG 2.03, I only see potential issues regarding the DEPENDENCIES
file name. In monorepos, we add _FRONTEND
or _BACKEND
suffixes. If we search for a fully matching DEPENDENCIES
, this could lead to issues. The INSTALL.md
issues from above could also be included in the repo structure check
@SebastianBezold I wouldn't say the reminder is odd since the check just follows TRG description which is very clear where the INSTALL.md should be located. At the moment I see that we either amend description first and check afterwards or recommend monorepo's guys to reference other INSTALL.md files of components within original one located at root.
We will get an exclusion mechanism which will make this green. We will also create a ticket to support monorepos and prioritize that accordingly
checks on repositories containing multiple components (e.g. frontend + backend) should not throw warnings regarding TRG 1.02 + TRG 2.03