This makes a few changes so that highfive will prefer matching the longest paths in the dirs map. In summary:
If there is an entry compiler and compiler/foo, and most of the changes are in compiler/foo, then it will choose the reviewers from compiler/foo.
Previously highfive would only look at the first two path components. That means an entry like src/tools/cargo wasn't working at all. This changes it so that it supports dirs entries of any length.
Previously highfive would consider any change under the compiler directory to only match the "compiler" entry in the dirs map. This means that all the things added in #356 weren't working at all. This changes it so that "compiler" is not special.
There was a special-case check for src/test that isn't necessary anymore.
This changes it so that dirs matching will also look for deleted lines/files.
This makes a few changes so that highfive will prefer matching the longest paths in the
dirsmap. In summary:compilerandcompiler/foo, and most of the changes are incompiler/foo, then it will choose the reviewers fromcompiler/foo.src/tools/cargowasn't working at all. This changes it so that it supportsdirsentries of any length.compilerdirectory to only match the"compiler"entry in the dirs map. This means that all the things added in #356 weren't working at all. This changes it so that "compiler" is not special.src/testthat isn't necessary anymore.dirsmatching will also look for deleted lines/files.