\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]",[2912,2915],{"name":2913,"color":2914},"bug","d73a4a",{"name":2916,"color":2917},"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.7462043,{"description":2924,"labels":2925,"number":2928,"owner":2876,"repository":2877,"state":2878,"title":2929,"updated_at":2930,"url":2931,"score":2932},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[2926,2927],{"name":2913,"color":2914},{"name":2868,"color":2869},4249,"[Bug] MultiForge: second forge can not be used","2024-10-25T17:33:00Z","https://github.com/woodpecker-ci/woodpecker/issues/4249",0.7518152,{"description":2934,"labels":2935,"number":2942,"owner":2876,"repository":2877,"state":2878,"title":2943,"updated_at":2944,"url":2945,"score":2946},"and address\r\n- https://github.com/woodpecker-ci/woodpecker/issues/3503 -> #3820\r\n- https://github.com/woodpecker-ci/woodpecker/pull/3733#issuecomment-2180578290\r\n- ...\r\n\r\nTests to run:\r\n- [ ] Run workflow with steps that should only run if the step before [failed,succeded] (could help with questions like: https://github.com/woodpecker-ci/woodpecker/pull/3846#discussion_r1686246455)\r\n- [ ] Services and check if it is started before the steps who need it ...\r\n- [ ] Make sure the Queue respect **labels** and dependencies correctly\r\n- [ ] ...",[2936,2939],{"name":2937,"color":2938},"tests","ACEA1E",{"name":2940,"color":2941},"summary","C3DC73",3819,"Create \"backend integration test\" framework","2024-11-05T23:18:48Z","https://github.com/woodpecker-ci/woodpecker/issues/3819",0.7568969,{"description":2948,"labels":2949,"number":2953,"owner":2876,"repository":2877,"state":2878,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Clear and concise description of the problem\n\nWould be nice to show expected time progress based on previous run times\n\n### Suggested solution\n\nShould calculate based on previous pipelines with similar params - pr/push (same branch)/tag\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.",[2950],{"name":2951,"color":2952},"feature","180DBE",1563,"Show expected pipeline/step run time","2023-02-16T07:03:25Z","https://github.com/woodpecker-ci/woodpecker/issues/1563",0.7620918,{"description":2959,"labels":2960,"number":2963,"owner":2876,"repository":2877,"state":2964,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Clear and concise description of the problem\r\n\r\nWoodpecker can support setting the `runtimeClassName` configuration for a pipeline step Pod. `runtimeClassName` specifies the alternative container runtime to use, which is useful when we need different runtime features, most notably CUDA support from NVIDIA’s runtime distributions.\r\n\r\nI’m new to Woodpecker and Go, but I’m willing to help if I can learn the codebase.\r\n\r\n### Suggested solution\r\n\r\nAdd a configurable `runtimeClass` property in `steps[].backend_options.kubernetes`. When this property is specified, use it as the `spec.runtimeClassName` of the created Pod.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nRuntime Class | Kubernetes: https://kubernetes.io/docs/concepts/containers/runtime-class/\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.",[2961,2962],{"name":2888,"color":2889},{"name":2874,"color":2872},3473,"closed","Support for setting runtime class on Kubernetes backend","2024-03-29T09:29:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3473",0.6974712,{"description":2970,"labels":2971,"number":2974,"owner":2876,"repository":2877,"state":2964,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Clear and concise description of the problem\n\nWhen committing with a structured message (e.g. following Conventional Commits specification), Woodpecker cramps the whole message together into one large string when displaying it in the repo commit list and the pipeline run title. This is usually pretty ugly and decreases readability. \r\n\r\nExample:\r\n\r\n\n\n### Suggested solution\n\nA new environment variable CI_COMMIT_MESSAGE_HEADER could be added which would be used to populate the strings mentioned above. This would of course require parsing the commit message first.\n\n### Alternative\n\nAlternatively, a UI section for the body and footer of the commit message could be added below the pipeline run title to display those variables. \r\n\r\nAll of the steps described above would still be necessary, but in addition, at least CI_COMMIT_MESSAGE_BODY (if one wants to treat body and footer as one) would have to be parsed and added as well.\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.",[2972,2973],{"name":2916,"color":2917},{"name":2951,"color":2952},1489,"Beautify display of commit messages with bodies and/or footers","2023-08-20T16:52:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1489",0.7115524,{"description":2980,"labels":2981,"number":2984,"owner":2876,"repository":2877,"state":2964,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### 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).",[2982,2983],{"name":2913,"color":2914},{"name":2916,"color":2917},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.7335446,["Reactive",2990],{},["Set"],["ShallowReactive",2993],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fchPlDoM6hkGCbpS5SbiSukDWkJmvEzGNfzz2IUlbUzE":-1},"/woodpecker-ci/woodpecker/3889"]