\r\n\n\n### Steps to reproduce\n\n.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n\"next-d126cf9e35\"\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"ui","46DEA2",4677,"woodpecker-ci","woodpecker","open","`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.71432567,{"description":2882,"labels":2883,"number":2890,"owner":2874,"repository":2875,"state":2876,"title":2891,"updated_at":2892,"url":2893,"score":2894},"I think we should have a look at https://nextcloud.com/contribute/ and chery-pick some ideas from that",[2884,2887],{"name":2885,"color":2886},"documentation","7D625D",{"name":2888,"color":2889},"enhancement","7E1FE4",4113,"Improve docs about starting to contribute","2024-09-15T09:47:05Z","https://github.com/woodpecker-ci/woodpecker/issues/4113",0.7565279,{"description":2896,"labels":2897,"number":2906,"owner":2874,"repository":2875,"state":2876,"title":2907,"updated_at":2908,"url":2909,"score":2910},"We could have a workspace preparation docker image that would be run as root and do necessary tasks to prepare everything so that the skip clone would work and also clone steps could be run as non-root images?\n\nMaybe even a woodpecker server could act as docker registry to serve container image for this so that it would work in instances that have no internet connection\n\n_Originally posted by @lafriks in https://github.com/woodpecker-ci/woodpecker/pull/5056#issuecomment-2784618118_",[2898,2901,2904],{"name":2899,"color":2900},"server","5D7A92",{"name":2902,"color":2903},"backend/docker","bfdadc",{"name":2905,"color":2903},"backend/kubernetes",5082,"Add workspace preparation hidden step before clone steps","2025-04-07T21:24:54Z","https://github.com/woodpecker-ci/woodpecker/issues/5082",0.75820106,{"description":2912,"labels":2913,"number":2916,"owner":2874,"repository":2875,"state":2876,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### Component\n\nserver\n\n### Describe the bug\n\nError when enabling Gitea repository in Woodpecker CI:\n\n`could not create/update repo in store. error=\"pq: duplicate key value violates unique constraint \\\"UQE_repos_name\\\"\"`\n\nThere are no records with forge_id 0 in orgs table where we had similar problems\n\n### Steps to reproduce\n\n1. Press \"Enable\" in repository list\n2. Webhook is created\n3. Record in database can not be updated (possible tries to insert new one instead of updating?)\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.3.0\"}\n```\n\n### Additional context\n\nPostgreSQL database, Gitea forge integration\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[2914,2915],{"name":2868,"color":2869},{"name":2899,"color":2900},4935,"Activating repository error that failed to activate becauce of UQE_repos_name constraint","2025-03-11T14:11:01Z","https://github.com/woodpecker-ci/woodpecker/issues/4935",0.7616179,{"description":2922,"labels":2923,"number":2927,"owner":2874,"repository":2875,"state":2876,"title":2928,"updated_at":2929,"url":2930,"score":2931},"we currently don't have a concept how to translate/interpreter the services into \"local backend\" and just ignore them.\r\n\r\nwe should have it that way so it works very similar to what the user know with docker or kube backend.",[2924,2925],{"name":2888,"color":2889},{"name":2926,"color":2903},"backend/local",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.7643807,{"description":2933,"labels":2934,"number":2938,"owner":2874,"repository":2875,"state":2876,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Clear and concise description of the problem\n\nIn a `Dockerfile` it is often necessary to connect to some resource (e.g. remote registry) and for that we need secrets.\r\n\r\nThere is no way to do this.\n\n### Suggested solution\n\nThe [official solution](https://docs.docker.com/engine/reference/builder/#run---mounttypesecret) is to use `RUN --mount=type=secret`. But that isn't supported by Woodpecker.\n\n### Alternative\n\n*There is no safe alternative.*\r\n\r\nUsing `ENV` is a terrible idea because they will be baked into the image. Unless they are passed into the docker build from the pipeline, but Woodpecker isn't able to do that currently.\r\n\r\nUsing `ARG` is also bad as they are [exposed](https://docs.docker.com/engine/reference/builder/#arg) in the docker history. So we can't use Woodpecker's `build_args` option.\n\n### Additional context\n\nI am sure some people will say that this is an easy problem to solve: \"just move that logic out of the Dockerfile and into the pipeline itself\".\r\n\r\nThat is not always possible. Some Dockerfiles are complex and must be used as-is. But they are managed by the pipeline, and the pipeline doesn't have any way to pass secrets (via environment variables or --mount=type=secret).\n\n### Validations\n\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[2935],{"name":2936,"color":2937},"feature","180DBE",2446,"Support --mount=type=secret when building a Dockerfile","2023-09-11T23:45:21Z","https://github.com/woodpecker-ci/woodpecker/issues/2446",0.7662863,{"description":2944,"labels":2945,"number":2947,"owner":2874,"repository":2875,"state":2876,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Component\n\nserver\n\n### Describe the bug\n\nWhile testing the ntfy plugin to send notifications after pipeline failure I wanted to use `CI_STEP_NAME` but it doesn't return a value. The other CI_STEP_* variables are not returning anything either.\r\n\r\nHere a example pipeline. I have added `CI_WORKFLOW_NAME` which does work.\r\n```\r\npipeline:\r\n deploy:\r\n image: alpine:latest\r\n commands:\r\n - exit 1\r\n\r\n notify_on_failure:\r\n image: codeberg.org/l-x/woodpecker-ntfy\r\n settings:\r\n url: https://ntfy.example.com/ci\r\n token:\r\n from_secret: ntfy_token\r\n title: Build failure\r\n priority: urgent\r\n icon: https://woodpecker-ci.org/img/logo.svg\r\n tags: x, robot\r\n message: >\r\n Workflow: ${CI_WORKFLOW_NAME}\r\n Step name: ${CI_STEP_NAME}\r\n Step status: ${CI_STEP_STATUS}\r\n Step started: ${CI_STEP_STARTED}\r\n Step finished: ${CI_STEP_FINISHED}\r\n when:\r\n status: [ failure ]\r\n```\n\n### System Info\n\n```shell\nVersion: next-02913fa7\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[2946],{"name":2888,"color":2889},1760,"`CI_STEP_*` environment variables do not return values","2024-10-05T23:54:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1760",0.7698734,{"description":2953,"labels":2954,"number":2957,"owner":2874,"repository":2875,"state":2958,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Clear and concise description of the problem\n\nWhen committing with a structured message (e.g. following Conventional Commits specification), Woodpecker cramps the whole message together into one large string when displaying it in the repo commit list and the pipeline run title. This is usually pretty ugly and decreases readability. \r\n\r\nExample:\r\n\r\n\n\n### Suggested solution\n\nA new environment variable CI_COMMIT_MESSAGE_HEADER could be added which would be used to populate the strings mentioned above. This would of course require parsing the commit message first.\n\n### Alternative\n\nAlternatively, a UI section for the body and footer of the commit message could be added below the pipeline run title to display those variables. \r\n\r\nAll of the steps described above would still be necessary, but in addition, at least CI_COMMIT_MESSAGE_BODY (if one wants to treat body and footer as one) would have to be parsed and added as well.\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[2955,2956],{"name":2871,"color":2872},{"name":2936,"color":2937},1489,"closed","Beautify display of commit messages with bodies and/or footers","2023-08-20T16:52:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1489",0.7396027,{"description":2964,"labels":2965,"number":2971,"owner":2874,"repository":2875,"state":2958,"title":2972,"updated_at":2973,"url":2974,"score":2975},"like the agent:\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/docker/Dockerfile.agent.multiarch#L21\r\n\r\nref https://docs.docker.com/engine/reference/builder/#healthcheck\r\n\r\nTODO:\r\n- [ ] add subcommand to server that can test against https://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/server/router/router.go#L69\r\n- [ ] use subcommand in container",[2966,2967,2968],{"name":2899,"color":2900},{"name":2936,"color":2937},{"name":2969,"color":2970},"good first issue","76ea72",1943,"Add an healthcheck to server container","2023-07-25T13:55:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1943",0.74186325,{"description":2977,"labels":2978,"number":2982,"owner":2874,"repository":2875,"state":2958,"title":2983,"updated_at":2984,"url":2985,"score":2986},"https://ci.woodpecker-ci.org/repos/3780/pipeline/20983/15\r\n\r\nbuild-deb-rpo errors with:\r\n```\r\nVERSION_NUMBER=0.0.0 nfpm package --config ./nfpm/agent.yaml --target dist --packager deb\r\nmatching \"./woodpecker-agent.service\": file does not exist\r\nmake: *** [Makefile:319: bundle-agent] Error 1\r\n```",[2979],{"name":2980,"color":2981},"build","6AB8BA",4152,"fix 'binary' workflow","2024-10-05T14:43:41Z","https://github.com/woodpecker-ci/woodpecker/issues/4152",0.744561,["Reactive",2988],{},["Set"],["ShallowReactive",2991],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fk3eqncepRIlupfFgBKq5_CuP0FXZyMyAeEqwZAAwiaI":-1},"/woodpecker-ci/woodpecker/4517"]