`maint` and `master` have been force-pushed to correct a mistake, again

Erlang News
1

maint was accidentally hard-reset to master about an hour ago and pushed upstream, and a few of our own commits were then based on incorrect versions of maint and master, so we’ve had to force-push earlier versions of maint and master to correct it.

No work has been lost and all pull requests we’ve merged from outside contributors are still there, but you will need to reset your local copy of the maint and master branches. We’re sorry for the inconvenience.

Original announcement: `maint` and `master` have been force-pushed to correct a mistake, again - Erlang News - Erlang Programming Language Forum - Erlang Forums

5 Likes
2

Did someone forget to protect the branch or something? :thinking:

1 Like
3

Thanks for the report.

Let’s just say I am sure improvements will be implemented, a gain (pun intended)

4

Sort of. These are two separate branches, where maint is always supposed to trail master, and unfortunately GitHub doesn’t allow us to express such a branch protection. We have a pre-push hook in the repository that checks this for us, scripts/pre-push, but it cannot protect anything unless it’s installed locally.

Someone hard-reset maint so that it had the same hash as master then pushed both to the main repository, without having the hook installed.

2 Likes