Please don't force-push to shared branches

[Seb via digitalmars-d-ldc]

On Saturday, 10 December 2016 at 17:03:51 UTC, David Nadlinger 
wrote:
> Dear all,
>
> The release-1.1.0 branch was force-pushed to recently. As a 
> hard and fast rule, don't do this on any branch you can 
> reasonably expect other people have checked out as well. There 
> are obviously exceptions (emergency fixups after committing big 
> files, breaking the history, etc.), but in such cases it would 
> still be considerate to then notify other people of what is 
> going on. This is common open-source folklore for a reason.
>
> Thanks.
>
>  — David

How about enabling force-push protection on GitHub?

https://github.com/blog/2051-protected-branches-and-required-status-checks