Hi, the tool is currently performing the check between A and B folders , opening an issue per every new term present in folder A or per every term newer in folder A compared with folder B.

If you can, we also need the creation of the issue, in the case when a term is deleted in folder A and still present in folder B.
This could happen when a glossary term is deprecated or evolved into something else.

Thanks!

The Italian SIG of the CNCF glossary has requested the capability to perform comparisons across different branches within the same repository, allowing selection of branches for both folder A and folder B.

Hi Simone!

I localize the Kubernetes documentation and use your tool to filter documents that need to be translated. The problem is that /content/xx in the K8s repository contains a lot of subdirectories, and I have to run the tool for each one of them. The recursive scanning option would be a solution, allowing the user to get a recursive scan report.

Thanks!

What would you like to be added?

An option for recursive scanning (probably in the form of an ENV variable of command line flag).

Why is this needed?

The user will be able to receive reports on file differences for all subdirectories of the directory from which the filtering started.