Philippe Miossec

Not heavily tested but you will find an attempt here: https://ci.appveyor.com/project/pmiossec/git-tfs/builds/50220367/artifacts with option `--ignore-eol`. If your feedback is good (because that's a dirty hack because we have to convert to...

If you are able to debug, what are the `tfsBranch.Path` and `filterRegex` values? And did you checked (for example with https://regex101.com/ ) that the branch path is matching the regex...

> It works using [https://regex101.com/](url) and with .NET application. From what I see, the regex is no working for me. You need to escape the 1st `$`. And there are...

And if you debug, what is the condition not satisfied? That can give you a clue... (Maybe ending with `/` or something similar)

Looking at the code, it is probable that `tfsBranch.Path` will end with a `/` (that's why I asked you to debug) So your RegEx will more be something like `^\$/Drive/(PRODUCTION/v2.\d{2}(-[\w-]+)?/*|DEV(/.*)?/*|Branches(/.*)?/*)$`...

It would be great indeed to support this option that brings more security and could prevent loosing work... But contrary to '--force-with-lease' which is crystal clear, reading carefully the documentation,...

> The way I understand it is that there's no chance to forcefully push changes w/o verifying those will not be lost locally. If that's the way it works (and...

If I have some time, I will do it (as I did for 'force-with-lease') and I will play with it to see if I better understand...

> The more I read about it, the more I feel that `--force-if-includes` should not be considered some optional luxurious option available to advanced users, but rather it should be...

Can you test the development version? I have the feeling that an improvement has been made to better handle this case but I can't find the issue or the PR...