Hello, Approximately two hours ago there was a force-push to the 1.12 branch, replacing commits 23f788d16f65 and 00c85e0031dc with 42ce10d135d6 and 39aac03cf6aa. Although this happened within less than 15 minutes and thus I would expect this to have minimal to zero impact to users of the repository, I'd like to apologize on behalf of the development team for any possible inconvenience this may cause any unlucky persons who pulled during that time frame.
And while I am at it, I'd like to remind everyone that force-pushing to a public Git repository depended upon by an indefinite number of people is extremely bad form and should only be done to solve a catastrophic mistake like accidentally merging incompatible branches. In Wesnoth's case, you *must* ask one or more of the repository administrators for help if you ever feel that force-pushing upstream to master or any other branch is necessary; the same applies to other Wesnoth-hosted repositories [1]. 1: https://github.com/wesnoth/ Finally, note that this policy does *not* apply to external repositories that are personal forks used to submit feature requests. Up to this point this has been a somewhat informal policy established early on after another repository administrator who shall remain nameless force-pushed a branch. However, in the interest of making this official, I have updated WesnothRepository [2] on the wiki with this information, and added a link to it from DeveloperGuide [3]. 2: http://wiki.wesnoth.org/WesnothRepository#Force-pushing_policy 3: http://wiki.wesnoth.org/DeveloperGuide#Commits -- Regards Ignacio R. Morelle <shadowm> _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
