yacy/.github/workflows/ant-build-selfhosted.yaml, branch masterYaCy search server with some extra patches
https://git.fennell.dev/yacy/atom?h=master2025-06-21T12:34:23Zfixed another bug in the docker build workflow, #22025-06-21T12:34:23ZMichael Peter Christenmc@yacy.net2025-06-21T12:34:23Zurn:sha1:5e9bfc1c70fa57a26ae99581442e91dad56cf093disabled selbhosted trigger2025-06-20T21:52:31ZMichael ChristenOrbiter@users.noreply.github.com2025-06-20T21:52:31Zurn:sha1:205497efdf2e30c24549f1464678e403927da946fixed workflow for ci process2023-08-31T16:03:04ZMichael Peter Christenmc@yacy.net2023-08-31T16:03:04Zurn:sha1:a3ca4eac08a31bb66f72d3fd0e900ae8e05352fefixed condition in workflow2023-03-05T00:40:08ZMichael Christenmc@yacy.net2023-03-05T00:40:08Zurn:sha1:84c797f53dc9a32acd68508b515bda6b40aa6ff0skip github jobs on forks2023-02-13T09:08:42ZThomas Kochthomas@koch.ro2023-02-13T09:08:42Zurn: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
removed ci script for nsis build2022-10-03T22:01:53ZMichael Peter Christenmc@yacy.net2022-10-03T22:01:53Zurn:sha1:79fc19e67e922387b20657f701e7635a71c30cd8add windows build to ci2022-10-03T16:23:03ZMichael Christenmc@yacy.net2022-10-03T16:23:03Zurn:sha1:55c181e5a08a1a5d25b25f76cf7839221742d6ffadded ci script2022-06-13T10:14:42ZMichael Peter Christenmc@yacy.net2022-06-13T10:14:42Zurn:sha1:c3307231d408908540b86b3e21406d9a542d8e5a