yacy/.github/workflows/ant-build-pull-request.yaml, branch master YaCy search server with some extra patches https://git.fennell.dev/yacy/atom?h=master 2026-07-12T11:24:43Z add solr9-jetty-bridge verification to CI 2026-07-12T11:24:43Z Michael Peter Christen mc@yacy.net 2026-07-12T11:24:43Z urn:sha1:92e0b111a0ce98964e4de3600d1a81643313ed7e We migrate to JDK 17 2026-07-10T20:47:39Z Michael Peter Christen mc@yacy.net 2026-07-10T20:47:39Z urn:sha1:dd0225bdde303cc739fed60c9aff28b63b868997 This is a hard requirement to be able to migrate to a more recent jetty version, which may happen sometime soon. fixed workflow for ci process/2 2023-08-31T16:05:58Z Michael Peter Christen mc@yacy.net 2023-08-31T16:05:58Z urn:sha1:ce4a2450da73956a85628b9eb9057b2aeaaec326 fixed condition in workflow 2023-03-05T00:40:08Z Michael Christen mc@yacy.net 2023-03-05T00:40:08Z urn:sha1:84c797f53dc9a32acd68508b515bda6b40aa6ff0 skip github jobs on forks 2023-02-13T09:08:42Z Thomas Koch thomas@koch.ro 2023-02-13T09:08:42Z urn:sha1:d9d1bc8c6569fdd3e801886248f9c6480c6ca1be I get scary emails from github about failed jobs for every commit pushed to my yacy fork. But the jobs should not run on my forked repo in the first place. This problem is not unique to yacy: https://github.com/actions/runner/issues/859 Alternatively every contributor could disable workflows in the settings of their fork repo: https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow added missing runs-on: ubuntu-latest 2022-06-13T16:54:12Z Michael Christen Orbiter@users.noreply.github.com 2022-06-13T16:54:12Z urn:sha1:c049c8d4a497d72a11d03ea6298e4564efc6655d CI Script to build after pull request 2022-06-13T13:36:00Z Michael Christen Orbiter@users.noreply.github.com 2022-06-13T13:36:00Z urn:sha1:be8ab9771f6c2dc3f9241493f541db99844f3eb5