\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]",[2890,2891],{"name":2866,"color":2867},{"name":2892,"color":2893},"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.7427503,{"description":2900,"labels":2901,"number":2906,"owner":2869,"repository":2870,"state":2871,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### 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]",[2902,2903],{"name":2866,"color":2867},{"name":2904,"color":2905},"server","5D7A92",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.75733703,{"description":2912,"labels":2913,"number":2916,"owner":2869,"repository":2870,"state":2871,"title":2917,"updated_at":2918,"url":2919,"score":2920},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[2914,2915],{"name":2866,"color":2867},{"name":2904,"color":2905},4249,"[Bug] MultiForge: second forge can not be used","2024-10-25T17:33:00Z","https://github.com/woodpecker-ci/woodpecker/issues/4249",0.76195204,{"description":2922,"labels":2923,"number":2930,"owner":2869,"repository":2870,"state":2871,"title":2931,"updated_at":2932,"url":2933,"score":2934},"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,2927],{"name":2925,"color":2926},"enhancement","7E1FE4",{"name":2928,"color":2929},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.7650859,{"description":2936,"labels":2937,"number":2941,"owner":2869,"repository":2870,"state":2871,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Clear and concise description of the problem\n\nIt would be great to have a search form available at `/admin`. For instances with more users (e.g. codeberg), the paginated load becomes quite an issue when searching for a particular user/org/repository.\r\n\r\n\n\n### Suggested solution\n\nAdd a search functionality, similar as in https://ci.codeberg.org/repos.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\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.",[2938,2939,2940],{"name":2904,"color":2905},{"name":2892,"color":2893},{"name":2925,"color":2926},3015,"Admin: Search functionality for users/repos/organizations","2023-12-27T07:56:01Z","https://github.com/woodpecker-ci/woodpecker/issues/3015",0.7672114,{"description":2947,"labels":2948,"number":2950,"owner":2869,"repository":2870,"state":2951,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWhen having a backend error in the config, i.e. a malformed env var, the step and build are marked as successful even though they should be marked as \"failed\". \r\n\r\n\r\n\r\n\r\nk8s backend\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6ab9f802\"}\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/master/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).",[2949],{"name":2866,"color":2867},1871,"closed","Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.71459895,{"description":2957,"labels":2958,"number":2966,"owner":2869,"repository":2870,"state":2951,"title":2967,"updated_at":2968,"url":2969,"score":2970},"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",[2959,2960,2963],{"name":2904,"color":2905},{"name":2961,"color":2962},"feature","180DBE",{"name":2964,"color":2965},"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.72333133,{"description":2972,"labels":2973,"number":2977,"owner":2869,"repository":2870,"state":2951,"title":2978,"updated_at":2979,"url":2980,"score":2981},"... move the details from https://woodpecker-ci.org/docs/next/usage/pipeline-syntax#images-from-private-registries to https://woodpecker-ci.org/docs/next/usage/registries and link there instead ...\r\n\r\nand also make it clear in the WebUI that registry tab in repo settings is only for pull images by the agent and not for push via some plugin",[2974],{"name":2975,"color":2976},"documentation","7D625D",1408,"Docs: move private registry infos","2023-10-17T08:31:09Z","https://github.com/woodpecker-ci/woodpecker/issues/1408",0.7473713,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fpFHQIFB42AdJrs5wDTvOaFsq1MmPjuO-uoqieHI6QmI":-1},"/woodpecker-ci/woodpecker/3801"]