I have a multibranch pipeline that scans the repository for new branches and runs tests on them.
First scenario:
One person created a branch feature/aaa/name and committed changes.
Another person created a branch feature/AAA/name and committed changes.
Something happened with the cache on the Jenkins master node, and the Git history got corrupted.

Second scenario:
Everyone commits following the pattern feature/AAA/name, feature/AAA/name1, feature/AAA/name2.
One person committed feature/aaa/name, and this caused an issue with the cache on the Jenkins master node, creating a folder aaa, into which all the previous work was placed, and as a result, the Git history got corrupted.
An error occurs: "cannot lock ref 'path': is at githash1 but expected githash2."