I am picking through the Github events. The force-push happens on this page:
https://api.github.com/repos/geoserver/geoserver/events?page=3
This push resets the head of 2.12.x to the last common commit
8e75e0856a360798ca2bf2a09989ff799f981720 (this I think is the force push):
{
"id": "6763084956",
"type": "PushEvent",
"actor": {
"id": 1278021,
"login": "afabiani",
"display_login": "afabiani",
"gravatar_id": "",
"url": "https://api.github.com/users/afabiani";,
"avatar_url": "https://avatars.githubusercontent.com/u/1278021?";
},
"repo": {
"id": 2751199,
"name": "geoserver/geoserver",
"url": "https://api.github.com/repos/geoserver/geoserver";
},
"payload": {
"push_id": 2075721342,
"size": 0,
"distinct_size": 0,
"ref": "refs/heads/2.12.x",
"head": "8e75e0856a360798ca2bf2a09989ff799f981720",
"before": "601a842e661450c908b5821bc5ae606a19954f3b",
"commits": [
]
},
"public": true,
"created_at": "2017-10-25T10:13:09Z",
"org": {
"id": 186522,
"login": "geoserver",
"gravatar_id": "",
"url": "https://api.github.com/orgs/geoserver";,
"avatar_url": "https://avatars.githubusercontent.com/u/186522?";
}
},
On 28/10/17 12:05, Torben Barsballe wrote:
Upon further investigation, it appears the following commits are now
missing from 2.12.x (There may be more, these are just the ones I have been
able to track down):
- 6544ca5
<https://github.com/geoserver/geoserver/commit/6544ca542a0a8b19a6bf905777a636b4ecad3e48>
- 5fbe3a2
<https://github.com/geoserver/geoserver/commit/5fbe3a21b0d5586996c908181b747e6b2eaf5789>
- e672ef0
<https://github.com/geoserver/geoserver/commit/e672ef07d0fb33c957050a887e73be9de9443986>
- 8a1e06a
<https://github.com/geoserver/geoserver/commit/8a1e06a418826bca527db0938dfbd204e2c2b470>
- 08c0d02
<https://github.com/geoserver/geoserver/commit/08c0d024873a5810ea80dfcfdd4fc7a52f6b40d3>
- 05352fe
<https://github.com/geoserver/geoserver/commit/05352fe7cec3b1ac8fcc4b7e144ed4aa78981748>
Based on the last commit in that tree that matches the current state of
2.12 (8e75e08
<https://github.com/geoserver/geoserver/commit/8e75e0856a360798ca2bf2a09989ff799f981720>)
, It seems likely that the commit that was force pushed is 74e01ef
<https://github.com/geoserver/geoserver/commit/74e01efe27511faea96f680242a79e7fdcbfd311>.
Alessio - any comments?
Torben
On Fri, Oct 27, 2017 at 3:48 PM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:
I've been seeing some errors today that suggest someone force pushed
changes to the geoserver/2.12.x branch.
At first I though it was just my local state that was out of order, but I
see similar issues on remote build servers. I'm also seeing some missing
commits on 2.12.x (Things that were backported from master but are no
longer there).
As far as I can tell, this happened sometime around October 19th - 25th.
Anyone who commited to the branch in that range may want to double check
the commit history, as no commits are showing up there anymore.
And as a reminder to everyone, NEVER force push to ANY release branch
(master, 2.12,x, etc) on a repository you do not personally own.
Thanks,
Torben
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
