\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]",[2882,2883],{"name":2866,"color":2867},{"name":2884,"color":2885},"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.72215813,{"description":2892,"labels":2893,"number":2897,"owner":2872,"repository":2873,"state":2874,"title":2898,"updated_at":2899,"url":2900,"score":2901},"### 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*",[2894],{"name":2895,"color":2896},"enhancement","7E1FE4",3285,"Buildin Environment variable which hold the milestone","2025-01-06T14:33:55Z","https://github.com/woodpecker-ci/woodpecker/issues/3285",0.7394241,{"description":2903,"labels":2904,"number":2906,"owner":2872,"repository":2873,"state":2874,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### 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.",[2905],{"name":2895,"color":2896},2373,"Per-workflow badge","2025-02-16T22:35:42Z","https://github.com/woodpecker-ci/woodpecker/issues/2373",0.74788743,{"description":2912,"labels":2913,"number":2915,"owner":2872,"repository":2873,"state":2916,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### 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]",[2914],{"name":2866,"color":2867},4140,"closed","Cannot connect to the Docker daemon","2024-09-24T04:18:14Z","https://github.com/woodpecker-ci/woodpecker/issues/4140",0.69311243,{"description":2922,"labels":2923,"number":2930,"owner":2872,"repository":2873,"state":2916,"title":2931,"updated_at":2932,"url":2933,"score":2934},"\r\n\r\n\r\nhttps://mashable.com/article/how-to-get-verified-mastodon",[2924,2927],{"name":2925,"color":2926},"documentation","7D625D",{"name":2928,"color":2929},"governance","A46EFE",3817,"Verified all Mastodon links","2024-07-15T18:37:37Z","https://github.com/woodpecker-ci/woodpecker/issues/3817",0.7245538,{"description":2936,"labels":2937,"number":2939,"owner":2872,"repository":2873,"state":2916,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### 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]",[2938],{"name":2866,"color":2867},3872,"variable CI_PIPELINE_DEPLOY_TASK is empty in woodpecker","2024-07-07T11:43:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3872",0.72662264,{"description":2945,"labels":2946,"number":2947,"owner":2872,"repository":2873,"state":2916,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Clear and concise description of the problem\n\nIt seems there's no API endpoint to sync repos? Would be great to have one. \r\n\r\n\n\n### Suggested solution\n\nAdd an API endpoint to sync new repos. \n\n### Alternative\n\n_No response_\n\n### Additional context\n\nI have some need for it within some automation which \r\n\r\n1. syncs new repos\r\n2. enables repos\r\n3. triggers a build by an automated commit\r\n\r\nApologies if I have overlooked the obvious - but I couldn't get it working even when invoking other endpoints (with the aim of triggering an implicit sync). \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/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.",[],1973,"Do we need a syncing repos via API? [-> no]","2023-07-12T09:04:10Z","https://github.com/woodpecker-ci/woodpecker/issues/1973",0.7306913,{"description":2953,"labels":2954,"number":2957,"owner":2872,"repository":2873,"state":2916,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\n1. Open developer console in browser\r\n2. Go to [repository activity](https://woodpecker.test.smthd.com/repos/1)\r\n3. Get two errors\r\n\r\nChrome:\r\n```\r\nindex-yc-Su7Fu.js:1\r\nTypeError: Cannot read properties of undefined (reading 'slice')\r\n at PipelineList.vue_vue_type_script_setup_true_lang-DuVPdeQs.js:1:4843\r\n at r (index-yc-Su7Fu.js:1:17606)\r\n at ya (index-yc-Su7Fu.js:1:26645)\r\n at ListItem.vue_vue_type_script_setup_true_lang-J7Q-CsOV.js:1:503\r\n at Object.r [as default] (index-yc-Su7Fu.js:1:17606)\r\n at Proxy.\u003Canonymous> (index-yc-Su7Fu.js:25:15333)\r\n at Es (index-yc-Su7Fu.js:1:17922)\r\n at wo.K [as fn] (index-yc-Su7Fu.js:1:42078)\r\n at wo.run (index-yc-Su7Fu.js:1:5674)\r\n at R.h.update (index-yc-Su7Fu.js:1:42357)\r\n```\r\n\r\nFirefox\r\n```\r\nindex-Hkbfabkk.js:1:15193\r\nTypeError: e.value.commit is undefined\r\n```\r\n\r\n### System Info\r\n\r\n```shell\r\nnext-acec955943\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 [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 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]\r\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).",[2955,2956],{"name":2866,"color":2867},{"name":2884,"color":2885},3012,"JS error on repository activity / pipelines list page","2023-12-27T15:25:46Z","https://github.com/woodpecker-ci/woodpecker/issues/3012",0.7308427,{"description":2963,"labels":2964,"number":2967,"owner":2872,"repository":2873,"state":2916,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Clear and concise description of the problem\r\n\r\nIt doesn't make much sense to duplicate the repositories in the `last visited` block too, if there are \u003C=4 in total\r\n\r\n\r\nBesides, odd number of items look not so smooth.\r\n\r\n### Suggested solution\r\n\r\nDo not display `last visited` block if there are only four repositories\r\n\r\n### Alternative\r\n\r\nUse [repos pinning](https://github.com/woodpecker-ci/woodpecker/issues/4424#issuecomment-2493207007)\r\n\r\n### Additional context\r\n\r\nWoodpecker `next-9f0611d1a1`, Gitea `1.22.4`, Postgres `16`\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 [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.",[2965,2966],{"name":2884,"color":2885},{"name":2895,"color":2896},4517,"Do not show last visited repos if there is less than 4 in total","2025-01-20T15:23:54Z","https://github.com/woodpecker-ci/woodpecker/issues/4517",0.735944,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f95Y0DAm1Gq7dCTqesYx6BT8konViBok9kzjhaTVzWTY":-1},"/woodpecker-ci/woodpecker/4918"]