Forgejo brings a similar concept called "Actions" where GH Actions can also be used.
The old action (https://github.com/koenrh/dnscontrol-action) worked perfectly fine. With a change to the new one it fails. (As in: It says Done but the output is a non 0 exit code)
resolved package url: https://github.com/DNSControl/dnscontrol/releases/download/v4.42.0/dnscontrol_4.42.0_linux_amd64.tar.gz
dnscontrol
4.42.0
No errors.
⚙ ::set-output:: output=CONCURRENTLY checking for 4 zone(s)\nSERIALLY checking for 0 zone(s)\nWaiting for concurrent checking(s) to complete...DONE\nCONCURRENTLY gathering records of 4 zone(s)\nSERIALLY gathering records of 0 zone(s)\nWaiting for concurrent gathering(s) to complete...DONE\n******************** Domain: XXXXX\n******************** Domain: XXXXX\n******************** Domain: XXXXX\n******************** Domain: XXXXX\nDone. 0 corrections.
This is a literal output (including \n). I suspect it has something to do with the ::set-output:: that is quite old and deprecated
qdrant/qdrant#6612
It looks like the set output is from the (2 year old) thollander/actions-comment-pull-request
Forgejo brings a similar concept called "Actions" where GH Actions can also be used.
The old action (https://github.com/koenrh/dnscontrol-action) worked perfectly fine. With a change to the new one it fails. (As in: It says Done but the output is a non 0 exit code)
This is a literal output (including \n). I suspect it has something to do with the ::set-output:: that is quite old and deprecated
qdrant/qdrant#6612
It looks like the set output is from the (2 year old) thollander/actions-comment-pull-request