\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]",[2882,2885],{"name":2883,"color":2884},"bug","d73a4a",{"name":2886,"color":2887},"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.729534,{"description":2894,"labels":2895,"number":2899,"owner":2872,"repository":2873,"state":2874,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Clear and concise description of the problem\r\n\r\nI need to check if a PR has a milestone set.\r\n\r\n### Suggested solution\r\n\r\nBest would be to have an environment variable which holds the name of the milestone.\r\n\r\n### Alternative\r\n\r\nI could use a command line tool or even curl to ask my forge. However this creates extra stuff to maintain, e. g. how login to the forge? On the other hand Woodpecker fetches already so many stuff from the forge, why not just provide that information too?\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.\r\n\r\n\r\n\r\n---\r\n*Sponsored by Kithara Software GmbH*",[2896],{"name":2897,"color":2898},"enhancement","7E1FE4",3285,"Buildin Environment variable which hold the milestone","2025-01-06T14:33:55Z","https://github.com/woodpecker-ci/woodpecker/issues/3285",0.7358787,{"description":2905,"labels":2906,"number":2911,"owner":2872,"repository":2873,"state":2874,"title":2912,"updated_at":2913,"url":2914,"score":2915},"e.g. like https://github.com/woodpecker-ci/woodpecker/pull/3086 create pull tags.\r\n\r\njust clean them up if the pull gets closed",[2907,2908],{"name":2897,"color":2898},{"name":2909,"color":2910},"build","6AB8BA",3087,"build: delete pr images on pull close","2023-12-31T07:28:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3087",0.7419678,{"description":2917,"labels":2918,"number":2923,"owner":2872,"repository":2873,"state":2874,"title":2924,"updated_at":2925,"url":2926,"score":2927},"https://github.com/woodpecker-ci/woodpecker/blob/4456da99c56437ef49c799a047ad3518023e6ce3/pipeline/rpc/peer.go#L54",[2919,2922],{"name":2920,"color":2921},"documentation","7D625D",{"name":2866,"color":2867},3322,"Rename Interface to actully reflect what it is used for","2024-02-07T00:03:34Z","https://github.com/woodpecker-ci/woodpecker/issues/3322",0.7434766,{"description":2929,"labels":2930,"number":2935,"owner":2872,"repository":2873,"state":2874,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Component\n\nagent\n\n### Describe the bug\n\nAt this line https://github.com/woodpecker-ci/woodpecker/blob/v2.7.1/pipeline/backend/kubernetes/kubernetes.go#L229 there is no `return err`, meaning that any errors from parsing backend_options will be silently discarded.\n\n### Steps to reproduce\n\nThe following pipeline will demonstrate the issue\r\n\r\n```yaml\r\nwhen:\r\n - event: push\r\n - event: manual\r\n\r\nsteps:\r\n - name: test\r\n image: alpine:3.13\r\n commands:\r\n - echo \"Testing\"\r\n backend_options:\r\n kubernetes:\r\n resources:\r\n requests:\r\n cpu: 1 # This should be a string, so it won't be set\r\n```\n\n### Expected behavior\n\nThe error should be propagated back to the user, and the step should not run. Ideally such an error should be caught during initial pipeline validation.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-3ce20912cd\"}\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]",[2931,2932],{"name":2883,"color":2884},{"name":2933,"color":2934},"backend/kubernetes","bfdadc",4106,"Kubernetes backend silently discards backend_options errors","2024-11-24T22:54:32Z","https://github.com/woodpecker-ci/woodpecker/issues/4106",0.7467483,{"description":2941,"labels":2942,"number":2944,"owner":2872,"repository":2873,"state":2945,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Component\n\nserver\n\n### Describe the bug\n\nIf connection broken while you are running pipeline manually, you'll get `unknown` error and panic on Server.\n\n### Steps to reproduce\n\n1. Run Forge\r\n2. Run Woodpecker server, log in\r\n3. Open some repository\r\n4. Click `Run pipeline`\r\n5. Turn off Forge / scale down to 0 / disallow WP-Forge connection via firewall\r\n6. Close `Trigger a manual pipeline run` dialog by pressing `Run pipeline` button\r\n7. See unknown error and not closed overlay\r\n[Error](https://github.com/user-attachments/assets/f71d13a4-2e9f-40b1-b49c-1f8e0e3be855)\r\n9. Check server logs and find `panic recovered`\r\n[server-panic.log](https://github.com/user-attachments/files/16317552/server-panic.log)\r\n\n\n### Expected behavior\n\n1. Should not be panic on server\r\n2. As dialog closes, overlay should disappear also\r\n3. More meaningful error than `unknown`\n\n### System Info\n\n```shell\n`2.7.0`, Gitea\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]",[2943],{"name":2883,"color":2884},3943,"closed","Improve error on manual run when connection with Forge lost","2024-08-07T07:31:19Z","https://github.com/woodpecker-ci/woodpecker/issues/3943",0.7203057,{"description":2951,"labels":2952,"number":2956,"owner":2872,"repository":2873,"state":2945,"title":2957,"updated_at":2958,"url":2959,"score":2960},"(Long term goal - wont rush of course)\r\n\r\n* [x] able to migrate issues & pulls\r\n* [x] able to push updates to github (push mirrors)\r\n* [ ] bot to mirror github interactions to codeberg (like [gopherbot](https://github.com/golang/go/wiki/gopherbot) do on golang repos ...)\r\n\r\n\r\n# You can react on this issue to vote?\r\n\r\n**To avoid spamming the issue please refrain from commenting.**\r\n\r\n:+1: = move to codeberg; :laughing: = don't care; :-1: = no\r\n\r\n\r\n## Some background\r\n\r\nThe main difference between Github and [codeberg.org](https://codeberg.org) is who is operating the SCM systems and the fact that the software which is used for Github is not FOSS. While Github is operated by Microsoft and using Github as SCM, [codeberg.org](https://codeberg.org) is operated by the [Codeberg e.V.](https://docs.codeberg.org/getting-started/what-is-codeberg/) (non profit org based in Germany) and is using [Gitea](https://github.com/go-gitea/gitea) a FOSS software as SCM. In the end, the question is who you want to trust / support and which software (Github vs Gitea) you prefer.\r\n",[2953],{"name":2954,"color":2955},"governance","A46EFE",602,"Move main dev to Codeberg","2023-11-29T12:43:57Z","https://github.com/woodpecker-ci/woodpecker/issues/602",0.7208401,{"description":2962,"labels":2963,"number":2965,"owner":2872,"repository":2873,"state":2945,"title":2966,"updated_at":2967,"url":2968,"score":2969},"to follow our rules ... (https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md#owners) here it goes:\r\n\r\n@woodpecker-ci/advisors @woodpecker-ci/maintainers\r\n\r\nOnly maintainers (& advisors) are eligible to vote or to be elected, and if somebody doesn't want to be elected please send comment in this thread. Every maintainer could send 2 or less votes to other maintainers on the following comments and cannot send the votes to them self. The voting is available from now **to 2022/12/31** or the point all people with vote rights have done so.\r\n\r\n---\r\nsee #633 for inspirations",[2964],{"name":2954,"color":2955},1467,"Voting for new owners between 2023/1/1 ~ 2023/12/31","2023-01-01T18:14:50Z","https://github.com/woodpecker-ci/woodpecker/issues/1467",0.7380761,{"description":2971,"labels":2972,"number":2973,"owner":2872,"repository":2873,"state":2945,"title":2974,"updated_at":2975,"url":2976,"score":2977},"We currently have a default event filter that if not defined adds a none cron event filter. As a user cannot expect this from reading the config I propose to remove this default events list from the event-filter.",[],1863,"Remove default pipeline events filter (currently filtering cron)","2023-06-21T16:12:22Z","https://github.com/woodpecker-ci/woodpecker/issues/1863",0.7386281,["Reactive",2979],{},["Set"],["ShallowReactive",2982],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f918FHPXFbwA45AGorsUXm_r0IouMF7hASBCbCyTFfrM":-1},"/woodpecker-ci/woodpecker/3817"]