\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]",[2015,2016],{"name":1985,"color":1986},{"name":2002,"color":2003},4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.78366673,{"description":2023,"labels":2024,"number":2026,"owner":1991,"repository":1992,"state":1993,"title":2027,"updated_at":2028,"url":2029,"score":2030},"### Component\n\nserver\n\n### Describe the bug\n\nRestarting a pipeline that failed due to missing secrets is not enough.\r\nI have seen it in a tag event.\r\n```\r\nsecret \"***\" not found or not allowed to be used\r\n```\r\nThen I added the secret and restarted the pipeline and the error changed to\r\n```\r\n[generic]\r\npipeline definition not found\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5a7e314f5a\"}\n```\n\n\n### Additional context\n\nMight be related to https://github.com/woodpecker-ci/woodpecker/issues/1678\n\n### Validations\n\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 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).",[2025],{"name":1985,"color":1986},2982,"Restarting a pipeline that failed due to missing secrets is not enough","2024-12-08T12:10:58Z","https://github.com/woodpecker-ci/woodpecker/issues/2982",0.7888092,{"description":2032,"labels":2033,"number":2036,"owner":1991,"repository":1992,"state":1993,"title":2037,"updated_at":2038,"url":2039,"score":2040},"### Clear and concise description of the problem\r\n\r\nRepos list used to be sorted by name. So, it was kinda static. One could remember at a subconscious level where some repo is. Like: it is somewhere \"one scroll from the top\" and then \"on the middle of the page\". So, after \"Repositories\" clicked, I do one scroll and move pointer to the center of the screen. Then, I find the repo visually, adjust position of the pointer and click.\r\n\r\nNow, this list is dynamic, it always changes. I even can do nothing, just hit F5 and there will be completely reordered list, just because my teammates push changes, PRs got merged or some cron jobs.\r\n\r\n\r\n### Suggested solution\r\n\r\nIt would be great \r\n1. to have sorting setting like in GitHub \r\n2. to have sorting order saved somewhere\r\n\r\n### Alternative\r\n\r\nBring back sorting by name.\r\n\r\n### Additional context\r\n\r\nWP `next-350082cd19`, Gitea `1.22.3`, Postgres `16`, Kubernetes `v1.30.6+k3s1`\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/4386#issuecomment-2491103809\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/4386#issuecomment-2491120805\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/4386#issuecomment-2491350932\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.",[2034,2035],{"name":2002,"color":2003},{"name":2005,"color":2006},4423,"Add sorting method to the repos list","2024-11-21T15:47:46Z","https://github.com/woodpecker-ci/woodpecker/issues/4423",0.7896519,{"description":2042,"labels":2043,"number":2047,"owner":1991,"repository":1992,"state":2048,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### Clear and concise description of the problem\n\nThe [docs](https://woodpecker-ci.org/docs/administration/setup) show that the agent needs access to the docker socket. It's good practice to use a proxy instead of exposing the entire socket. The most common is the [\"tecnativa\" proxy](https://github.com/Tecnativa/docker-socket-proxy) .\r\n\r\nI assume that at the very least, an agent creates new containers, so needs access to the \"containers\" endpoint. Presumably it needs other endpoints too.\n\n### Suggested solution\n\nPlease consider *documenting which parts of the docker api are needed by the agent*. Then we could use the docker socket proxy to allow those and restrict the others.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nThese are [the docker api's endpoints](https://github.com/Tecnativa/docker-socket-proxy#grant-or-revoke-access-to-certain-api-sections):\r\n- typically allowed:\r\n - EVENTS\r\n - PING\r\n - VERSION\r\n- security-critical and so typically not allowed:\r\n - AUTH\r\n - SECRETS\r\n - POST\r\n- other\r\n - BUILD\r\n - COMMIT\r\n - CONFIGS\r\n - CONTAINERS\r\n - DISTRIBUTION\r\n - EXEC\r\n - GRPC\r\n - IMAGES\r\n - INFO\r\n - NETWORKS\r\n - NODES\r\n - PLUGINS\r\n - SERVICES\r\n - SESSION\r\n - SWARM\r\n - SYSTEM\r\n - TASKS\r\n - VOLUMES\r\n\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.",[2044],{"name":2045,"color":2046},"feature","180DBE",1917,"closed","Use woodpecker with docker socket proxy","2023-08-20T16:09:23Z","https://github.com/woodpecker-ci/woodpecker/issues/1917",0.7341686,{"description":2054,"labels":2055,"number":2057,"owner":1991,"repository":1992,"state":2048,"title":2058,"updated_at":2059,"url":2060,"score":2061},"It would be nice to have an env var like `CI_COMMIT_PULL_REQUEST_LABELS` containing a list of all set labels of a PR as a comma separated string. This would allow a user to filter steps and pipelines with https://woodpecker-ci.org/docs/next/usage/pipeline-syntax#evaluate to only be executed if a specific label is set or is not set. \r\n\r\nFor example the quite time consuming task of building docker images for PRs could be skipped by default and only be activated if the corresponding label was set by a maintainer.\r\n\r\nLater with the support of label changes triggering pipelines like suggested in https://github.com/woodpecker-ci/woodpecker/issues/286#issuecomment-1116699790 a pipeline could immediately be executed in case a label got added.",[2056],{"name":2005,"color":2006},1308,"Add env var with labels from PR","2023-03-17T02:43:07Z","https://github.com/woodpecker-ci/woodpecker/issues/1308",0.73717636,{"description":2063,"labels":2064,"number":2069,"owner":1991,"repository":1992,"state":2048,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### Clear and concise description of the problem\n\nE.g. in https://github.com/woodpecker-ci/woodpecker/blob/69ec44075cba1bd2f45a186814386e390614826f/server/remote/gitea/gitea.go#L44 it is 50. If the instance/forge doesn't allow 50 items, this is a problem. Gitea for example has an API endpoint that allows to get the maximum: https://try.gitea.io/api/swagger#/settings/getGeneralAPISettings\n\n### Suggested solution\n\nFetch the maximum and change it if needed.\n\n### Alternative\n\n_No response_\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.",[2065,2068],{"name":2066,"color":2067},"forge/gitea","E96280",{"name":2005,"color":2006},1038,"List size requested from forge should be dynamic","2023-10-24T06:38:39Z","https://github.com/woodpecker-ci/woodpecker/issues/1038",0.75369596,{"description":2075,"labels":2076,"number":2082,"owner":1991,"repository":1992,"state":2048,"title":2083,"updated_at":2084,"url":2085,"score":2086},"\r\n\r\nthe default url is `https://woodpecker-ci.org/docs/next/administration/backends/docker` and that should remain.\r\n\r\nbut if it is `local` or `kubernetes` it would be nice to show different urls towards `https://woodpecker-ci.org/docs/next/administration/backends/local` and `https://woodpecker-ci.org/docs/next/administration/backends/kubernetes`.",[2077,2078,2079],{"name":2002,"color":2003},{"name":2005,"color":2006},{"name":2080,"color":2081},"good first issue","76ea72",4137,"WebUI: agent edit/detail view: change the **HELP** url based on the backend","2024-10-11T23:12:07Z","https://github.com/woodpecker-ci/woodpecker/issues/4137",0.7674715,{"description":2088,"labels":2089,"number":2093,"owner":1991,"repository":1992,"state":2048,"title":2094,"updated_at":2095,"url":2096,"score":2097},"as title",[2090],{"name":2091,"color":2092},"build","6AB8BA",3590,"build: release windows binarys in zip file not tar.gz","2024-07-14T20:59:46Z","https://github.com/woodpecker-ci/woodpecker/issues/3590",0.7751783,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"KnrBdie9YM6iiWLP0w8ZbfP-4xYWkMast0JD6XTK_po":-1},"/woodpecker-ci/woodpecker/4792"]