6543
@ktpx that's off topic ... but: merge target branch locally or rebase and push PS: conflict detections do not work like merge - as it would be a merge otherwhise...
I'm not aware of any draft so I would say go on and it is yours ;) If you need help just ask. for the UI side I would have...
for beginner it's easy to just clone and start ... not sure why we should complicate onboarding ...
this migth happen if the service has no commands (as usual) and no environment set, it will count as plugin. and plugins get set there working directory. using the `directory`...
hmm :thinking: well that's not completely wrong ... it has to be improved. 1. document it 2. make it work with WORKDIR set for services ... but we have to...
I would say https://github.com/woodpecker-ci/woodpecker/issues/3993#issuecomment-2353089981 + mentioned issue should fix it ... PS: feel free to open a new one if something similar appears and reference this issue here
before reading more into this pull code and issue, tow important questions: - why did you touch the `pipeline/*` code at all? I thought we already allow to have environment...
well if we implement it the right way ... you can create a e.g. build-service step then a test-with-service step that depends on the build-service step and make the service.steps=test-with-service...
the spec describes a client **may** wana request old missing keys: https://matrix.org/docs/matrix-concepts/end-to-end-encryption/#key-sharing so the key exchange has to be implemented in that way