Add --force-if-includes option or default to make git push --force-with-lease setting safer

[npbenjohnson]

Add --force-if-includes setting or default to prevent unexpected work loss when --force-with-lease is enable in settings.

From official git docs:

A general note on safety: supplying this option without an expected value, i.e. as --force-with-lease or --force-with-lease= interacts very badly with anything that implicitly runs git fetch on the remote to be pushed to in the background, e.g. git fetch origin on your repository in a cronjob.

Other git settings such as "Autofetch" and "Fetch on pull" make vscode especially likely to unexpectedly drop remote changes when performing a force-with-lease push.

Eloquent explanation of flags, tradeoffs, and why unexpected losses could occur: https://stackoverflow.com/a/65839129/1331851

[vscode-triage-bot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscode-triage-bot]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscodenpa]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!