Program scan all files and matches all ifft blocks, not checking if a change happened there or not
Closed this issue · 0 comments
thiagosantos0 commented
This is not the expected behavior. Right now the tool triggers a warning even when the a change isn't in a IFFT block. In fact the tool is triggering even if it we don't have a new change.
In the previous image we can see that the program can successfully identify a IFFT block. The is not a new change and even thought the tool is triggering. The following image shows that we don't have any unstaged file (change file that was not added for a commit yet):
