\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]",[3168,3169],{"name":3152,"color":3153},{"name":3170,"color":3171},"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":3178,"labels":3179,"number":3183,"owner":3158,"repository":3159,"state":3160,"title":3184,"updated_at":3185,"url":3186,"score":3187},"### 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.",[3180],{"name":3181,"color":3182},"enhancement","7E1FE4",2373,"Per-workflow badge","2025-02-16T22:35:42Z","https://github.com/woodpecker-ci/woodpecker/issues/2373",0.74788743,{"description":3189,"labels":3190,"number":3192,"owner":3158,"repository":3159,"state":3193,"title":3194,"updated_at":3195,"url":3196,"score":3197},"### 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]",[3191],{"name":3152,"color":3153},4140,"closed","Cannot connect to the Docker daemon","2024-09-24T04:18:14Z","https://github.com/woodpecker-ci/woodpecker/issues/4140",0.69311243,{"description":3199,"labels":3200,"number":3207,"owner":3158,"repository":3159,"state":3193,"title":3208,"updated_at":3209,"url":3210,"score":3211},"\r\n\r\n\r\nhttps://mashable.com/article/how-to-get-verified-mastodon",[3201,3204],{"name":3202,"color":3203},"documentation","7D625D",{"name":3205,"color":3206},"governance","A46EFE",3817,"Verified all Mastodon links","2024-07-15T18:37:37Z","https://github.com/woodpecker-ci/woodpecker/issues/3817",0.7245538,{"description":3213,"labels":3214,"number":3216,"owner":3158,"repository":3159,"state":3193,"title":3217,"updated_at":3218,"url":3219,"score":3220},"### 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]",[3215],{"name":3152,"color":3153},3872,"variable CI_PIPELINE_DEPLOY_TASK is empty in woodpecker","2024-07-07T11:43:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3872",0.7266227,{"description":3222,"labels":3223,"number":3224,"owner":3158,"repository":3159,"state":3193,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### 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":3230,"labels":3231,"number":3234,"owner":3158,"repository":3159,"state":3193,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### 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).",[3232,3233],{"name":3152,"color":3153},{"name":3170,"color":3171},3012,"JS error on repository activity / pipelines list page","2023-12-27T15:25:46Z","https://github.com/woodpecker-ci/woodpecker/issues/3012",0.73084265,{"description":3240,"labels":3241,"number":3244,"owner":3158,"repository":3159,"state":3193,"title":3245,"updated_at":3246,"url":3247,"score":3248},"### 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.",[3242,3243],{"name":3170,"color":3171},{"name":3181,"color":3182},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,{"description":3250,"labels":3251,"number":3253,"owner":3158,"repository":3159,"state":3193,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### 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]",[3252],{"name":3152,"color":3153},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.73598033,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f95Y0DAm1Gq7dCTqesYx6BT8konViBok9kzjhaTVzWTY":-1},"/woodpecker-ci/woodpecker/4918"]