\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]",[2001,2002],{"name":1985,"color":1986},{"name":2003,"color":2004},"ui","46DEA2",4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7347797,{"description":2011,"labels":2012,"number":2019,"owner":1991,"repository":1992,"state":1993,"title":2020,"updated_at":2021,"url":2022,"score":2023},"e.g. like https://github.com/woodpecker-ci/woodpecker/pull/3086 create pull tags.\r\n\r\njust clean them up if the pull gets closed",[2013,2016],{"name":2014,"color":2015},"enhancement","7E1FE4",{"name":2017,"color":2018},"build","6AB8BA",3087,"build: delete pr images on pull close","2023-12-31T07:28:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3087",0.73953885,{"description":2025,"labels":2026,"number":2028,"owner":1991,"repository":1992,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### Clear and concise description of the problem\r\n\r\nI need to check if a PR has a milestone set.\r\n\r\n### Suggested solution\r\n\r\nBest would be to have an environment variable which holds the name of the milestone.\r\n\r\n### Alternative\r\n\r\nI could use a command line tool or even curl to ask my forge. However this creates extra stuff to maintain, e. g. how login to the forge? On the other hand Woodpecker fetches already so many stuff from the forge, why not just provide that information too?\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\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]\r\n- [x] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\r\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\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.\r\n\r\n\r\n\r\n---\r\n*Sponsored by Kithara Software GmbH*",[2027],{"name":2014,"color":2015},3285,"Buildin Environment variable which hold the milestone","2025-01-06T14:33:55Z","https://github.com/woodpecker-ci/woodpecker/issues/3285",0.74809873,{"description":2034,"labels":2035,"number":2037,"owner":1991,"repository":1992,"state":1993,"title":2038,"updated_at":2039,"url":2040,"score":2041},"### Clear and concise description of the problem\r\n\r\nWe're using multiple workflows to test different parts of a project, and would like to have badges showing us the state of each part\r\n\r\n### Suggested solution\r\n\r\nProvide per-workflow badges and UI tabs\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\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]\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\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.",[2036],{"name":2014,"color":2015},2373,"Per-workflow badge","2025-02-16T22:35:42Z","https://github.com/woodpecker-ci/woodpecker/issues/2373",0.7492061,{"description":2043,"labels":2044,"number":2054,"owner":1991,"repository":1992,"state":1993,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### Clear and concise description of the problem\r\n\r\nas of https://github.com/woodpecker-ci/woodpecker/pull/2691\r\n\r\n~~blocked by https://github.com/swaggo/swag/issues/386~~ -> https://github.com/woodpecker-ci/woodpecker/pull/3897\r\n\r\n### Suggested solution\r\n\r\nauto-generate client from swagger docs so we don't have to do it manually\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\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]\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\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.",[2045,2046,2049,2052],{"name":2014,"color":2015},{"name":2047,"color":2048},"refactor","4f8cc9",{"name":2050,"color":2051},"blocked","AF9796",{"name":2053,"color":1989},"lib",3053,"Generate sdk from swagger","2024-07-13T12:58:23Z","https://github.com/woodpecker-ci/woodpecker/issues/3053",0.7520574,{"description":2060,"labels":2061,"number":2063,"owner":1991,"repository":1992,"state":2064,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Component\n\nagent\n\n### Describe the bug\n\nKubernetes rke2r1\r\nCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\r\n\r\nand obsviusly the pipeline don't run\n\n### Steps to reproduce\n\nremove old version and re-install via helm char new version\r\n\r\nhelm uninstall woodpecker -n woodpecker && \\\r\nkubectl delete ns woodpecker && \\\r\nhelm upgrade --install woodpecker woodpecker/woodpecker --namespace woodpecker --create-namespace -f woodpecker-values.yaml\n\n### Expected behavior\n\nthe pipeline has to run \n\n### System Info\n\n```shell\n{\r\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n \"version\": \"2.7.1\"\r\n}\n```\n\n\n### Additional context\n\nStep Logs\r\n\r\n1) clone\r\n\r\n\r\n2) on my first step build-publish\r\n\r\n\r\n\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]",[2062],{"name":1985,"color":1986},4140,"closed","Cannot connect to the Docker daemon","2024-09-24T04:18:14Z","https://github.com/woodpecker-ci/woodpecker/issues/4140",0.6963954,{"description":2070,"labels":2071,"number":2073,"owner":1991,"repository":1992,"state":2064,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### Component\n\nagent\n\n### Describe the bug\n\nOn an arm64 agent (Raspberry Pi 4b+), the clone step fails when the container is running in podman:\r\n\r\n```\r\n+ git init -b main\r\nInitialized empty Git repository in /woodpecker/src/git.vdx.hu/voidcontext/nix-config/.git/\r\n+ git config --global --replace-all safe.directory /woodpecker/src/git.vdx.hu/voidcontext/nix-config\r\n+ git remote add origin https://git.vdx.hu/voidcontext/nix-config.git\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +a4b83a869d6366bf24921b8f4f3f5836f806f57e:fatal: unable to access 'https://git.vdx.hu/voidcontext/nix-config.git/': Could not resolve host: git.vdx.hu\r\nexit status 128\r\n```\r\n\r\nThe server is on a different server (on amd64).\r\n\r\nExample: https://woodpecker.ci.vdx.hu/repos/109/pipeline/119/5\r\n\r\nThe same pipeline is successful on an amd64 agent (Kubernetes on a 3rd machine).\r\n\r\nThe issue seems to be similar to https://github.com/woodpecker-ci/woodpecker/issues/1407 which has been closed bacause of inactivity.\n\n### Steps to reproduce\n\n1) install server on amd64 machine (A)\r\n2) install agent on arm64 machine (B) using Docker backend that points to a docker compatible podman socket.\r\n3) Run pipeline\n\n### Expected behavior\n\nGit is able to resolve the host as it has a public DNS record.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\r\n```\n```\n\n\n### Additional context\n\nUnfortunately I wasn't able to test this on `next`.\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]",[2072],{"name":1985,"color":1986},3892,"Git clone step fails with \"Could not resolve host\" error when running fetch","2024-07-18T22:49:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3892",0.728357,{"description":2079,"labels":2080,"number":2082,"owner":1991,"repository":1992,"state":2064,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nI am testing version 2.6 in my development environment, so I updated an application code to use \r\n```- evaluate: CI_PIPELINE_DEPLOY_TASK == \"sre-dummy-rest-app\"```\r\ninstead of the 'task:' filter.\r\nIn my github hooks payload I get: \r\n\r\nBut the CI_PIPELINE_DEPLOY_TASK is empty and woodpecker is not running the steps that it should run.\r\n\r\n### Steps to reproduce\r\n\r\nUsing :\r\n``` \r\nwhen:\r\n - evaluate: CI_PIPELINE_DEPLOY_TASK == \"value\" \r\n```\r\n\r\nInstead of:\r\n`task: \"value\"`\r\n\r\n### Expected behavior\r\n\r\nRun with the variable as it should run with the filter in previous versions.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\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.\r\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]",[2081],{"name":1985,"color":1986},3872,"variable CI_PIPELINE_DEPLOY_TASK is empty in woodpecker","2024-07-07T11:43:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3872",0.7313778,{"description":2088,"labels":2089,"number":2096,"owner":1991,"repository":1992,"state":2064,"title":2097,"updated_at":2098,"url":2099,"score":2100},"\r\n\r\n\r\nhttps://mashable.com/article/how-to-get-verified-mastodon",[2090,2093],{"name":2091,"color":2092},"documentation","7D625D",{"name":2094,"color":2095},"governance","A46EFE",3817,"Verified all Mastodon links","2024-07-15T18:37:37Z","https://github.com/woodpecker-ci/woodpecker/issues/3817",0.736733,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"95Y0DAm1Gq7dCTqesYx6BT8konViBok9kzjhaTVzWTY":-1},"/woodpecker-ci/woodpecker/4918"]