\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]",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"ui","46DEA2",4677,"woodpecker-ci","woodpecker","open","`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7693425,{"description":2882,"labels":2883,"number":2888,"owner":2874,"repository":2875,"state":2876,"title":2889,"updated_at":2890,"url":2891,"score":2892},"### Clear and concise description of the problem\n\nWhen following the logs of a step I would like the UI to automatically select the next step if the step I am currently looking at has finished.\n\n### Suggested solution\n\nAutomatically jump to the next step when currently visible step status changes to successfully finished.\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 [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.",[2884,2885],{"name":2871,"color":2872},{"name":2886,"color":2887},"enhancement","7E1FE4",3801,"Log jump to next step when finished","2024-06-24T11:59:39Z","https://github.com/woodpecker-ci/woodpecker/issues/3801",0.7710409,{"description":2894,"labels":2895,"number":2900,"owner":2874,"repository":2875,"state":2876,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### 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]",[2896,2897],{"name":2868,"color":2869},{"name":2898,"color":2899},"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.7755316,{"description":2906,"labels":2907,"number":2909,"owner":2874,"repository":2875,"state":2876,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### 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).",[2908],{"name":2868,"color":2869},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.7853711,{"description":2915,"labels":2916,"number":2928,"owner":2874,"repository":2875,"state":2876,"title":2929,"updated_at":2930,"url":2931,"score":2932},"https://github.com/woodpecker-ci/woodpecker/tree/main/docs/docs/30-administration\r\n\r\nhttps://woodpecker-ci.org/docs/administration/forges/forgejo#registration\r\nhttps://woodpecker-ci.org/docs/administration/forges/gitea#registration\r\n\r\nonly mention user-oauth2-apps but if you are provider of both the forge and woodpecker itself in most cases you want the system-wiede-oauth2-app",[2917,2920,2923,2926],{"name":2918,"color":2919},"documentation","7D625D",{"name":2921,"color":2922},"forge/gitea","E96280",{"name":2924,"color":2925},"good first issue","76ea72",{"name":2927,"color":2922},"forge/forgejo",3818,"Update forgejo/gitea docs to mention system wide Oauth2 Apps","2024-06-22T16:16:36Z","https://github.com/woodpecker-ci/woodpecker/issues/3818",0.78572124,{"description":2934,"labels":2935,"number":2938,"owner":2874,"repository":2875,"state":2939,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### 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.",[2936,2937],{"name":2921,"color":2922},{"name":2886,"color":2887},1038,"closed","List size requested from forge should be dynamic","2023-10-24T06:38:39Z","https://github.com/woodpecker-ci/woodpecker/issues/1038",0.73642534,{"description":2945,"labels":2946,"number":2948,"owner":2874,"repository":2875,"state":2939,"title":2949,"updated_at":2950,"url":2951,"score":2952},"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.",[2947],{"name":2886,"color":2887},1308,"Add env var with labels from PR","2023-03-17T02:43:07Z","https://github.com/woodpecker-ci/woodpecker/issues/1308",0.7412125,{"description":2954,"labels":2955,"number":2959,"owner":2874,"repository":2875,"state":2939,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Clear and concise description of the problem\n\nThe only way for a plugin or another container to communicate to other containers or with the build process is to create files in the repository, which is a bad idea. \n\n### Suggested solution\n\nA way for plugins or even containers to generate outputs which can be accessed from other containers or the users. Similar to GitHub Actions: https://docs.github.com/en/actions/using-jobs/defining-outputs-for-jobs\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.",[2956],{"name":2957,"color":2958},"feature","180DBE",913,"Allow containers/plugins to generate outputs","2023-08-20T20:25:25Z","https://github.com/woodpecker-ci/woodpecker/issues/913",0.75918955,{"description":2965,"labels":2966,"number":2970,"owner":2874,"repository":2875,"state":2939,"title":2971,"updated_at":2972,"url":2973,"score":2974},"\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`.",[2967,2968,2969],{"name":2871,"color":2872},{"name":2886,"color":2887},{"name":2924,"color":2925},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.7625472,{"description":2976,"labels":2977,"number":2980,"owner":2874,"repository":2875,"state":2939,"title":2981,"updated_at":2982,"url":2983,"score":2984},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe spaces in task output should be kept.\r\n\r\n\r\n\n\n### System Info\n\n```shell\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"next-9feb6be9\"\n```\n\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 reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[2978,2979],{"name":2868,"color":2869},{"name":2871,"color":2872},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.7712561,["Reactive",2986],{},["Set"],["ShallowReactive",2989],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKnrBdie9YM6iiWLP0w8ZbfP-4xYWkMast0JD6XTK_po":-1},"/woodpecker-ci/woodpecker/4792"]