\r\n \u003Clink rel=\"alternate icon\" type=\"image/png\" href=\"/favicons/favicon-light-default.png\" id=\"favicon-png\" />\r\n \u003Clink rel=\"icon\" type=\"image/svg+xml\" href=\"/favicons/favicon-light-default.svg\" id=\"favicon-svg\" />\r\n \u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\" />\r\n \u003Cmeta name=\"theme-color\" content=\"#65a30d\" />\r\n \u003Ctitle>Woodpecker\u003C/title>\r\n \u003Cscript type=\"\" src=\"/web-config.js\">\u003C/script>\r\n \u003Cscript type=\"module\" crossorigin src=\"/assets/index-4b7b57db.js\">\u003C/script>\r\n \u003Clink rel=\"stylesheet\" href=\"/assets/index-f123c06a.css\">\r\n \u003C/head>\r\n \u003Cbody>\r\n \u003Cdiv id=\"app\">\u003C/div>\r\n\r\n \u003C/body>\r\n\u003C/html>\r\n```\r\n\r\nThat is basically an \"empty\" page. Let's look at the response code:\r\n```\r\n$ curl -I http://localhost:8000/foo\r\nHTTP/1.1 200 OK\r\nX-Woodpecker-Version: next-45319b24\r\n# ...etc.\r\n```\r\n\r\nThat should have returned 404.\r\n\r\nNow let's request a non-existent API endpoint:\r\n```\r\n$ curl -I http://localhost:8000/api/bar\r\nHTTP/1.1 200 OK\r\nX-Woodpecker-Version: next-45319b24\r\n# ...etc.\r\n```\r\n\r\nSame thing.\r\n\r\nNow let's request a real API endpoint, for healthchecks:\r\n```\r\n$ curl http://localhost:8000/api/healthz\r\n\u003C!DOCTYPE html>\r\n\u003Chtml lang=\"en\">\r\n # ...\r\n\u003C/html>\r\n\r\n$ curl -I http://localhost:8000/api/healthz\r\nHTTP/1.1 200 OK\r\nX-Woodpecker-Version: next-45319b24\r\n# ...etc.\r\n```\r\n\r\nSame thing. Also, it should not return a page, only a REST response.\r\n\r\nClean up:\r\n```\r\n$ apk delete curl\r\n$ exit\r\n```\r\n\r\nSummary:\r\n- both existent and non-existent endpoints and pages respond with 200\r\n- that means the `/api/healthz` endpoint is not working: it's a \"proof of life\" rather than \"proof of health\"\r\n- and the health endpoint should only return a json REST response, not a page\r\n\r\n### System Info\r\n\r\n```shell\r\nversion next-45319b24-alpine\r\ndockerised\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).",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"server","5D7A92",1947,"woodpecker-ci","woodpecker","open","All pages and API endpoints (including non-existent ones) return 200","2025-03-16T13:50:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1947",0.782124,{"description":2880,"labels":2881,"number":2886,"owner":2872,"repository":2873,"state":2874,"title":2887,"updated_at":2888,"url":2889,"score":2890},"Restarting PR pipelines after the PR was closed, or approving them and running them that way should be prevented.",[2882,2883],{"name":2869,"color":2870},{"name":2884,"color":2885},"enhancement","7E1FE4",1759,"Prevent PR pipelines from running when PR got closed already","2023-08-20T16:37:21Z","https://github.com/woodpecker-ci/woodpecker/issues/1759",0.78459084,{"description":2892,"labels":2893,"number":2901,"owner":2872,"repository":2873,"state":2902,"title":2903,"updated_at":2904,"url":2905,"score":2906},"if you for example use \"espaniol\" witch is not fully translated strings are just hidden\r\n\r\nI expect an english word in case the current locales do not provide the string \r\n\r\nfollowup of #912",[2894,2895,2898],{"name":2866,"color":2867},{"name":2896,"color":2897},"ui","46DEA2",{"name":2899,"color":2900},"ux","fef2c0",1313,"closed","Locales dont have fallback","2022-10-23T00:26:08Z","https://github.com/woodpecker-ci/woodpecker/issues/1313",0.73146534,{"description":2908,"labels":2909,"number":2920,"owner":2872,"repository":2873,"state":2902,"title":2921,"updated_at":2922,"url":2923,"score":2924},"use locales for strings so we can make it translatable\r\n- [x] add locales framework (#912)\r\n- [ ] user is able to select/set language ( #1305)\r\n- [x] decide on translation platform\r\n - [ ] [Crowdin](https://crowdin.com/)\r\n - [x] [Weblate](https://weblate.org/en/)\r\n - [ ] [pontoon](https://pontoon.mozilla.org/)\r\n- [x] add ci pipeline that upload & download from translation platform",[2910,2911,2914,2917],{"name":2896,"color":2897},{"name":2912,"color":2913},"feature","180DBE",{"name":2915,"color":2916},"translation","F51C68",{"name":2918,"color":2919},"summary","C3DC73",258,"Locales","2022-10-21T19:58:38Z","https://github.com/woodpecker-ci/woodpecker/issues/258",0.75631577,{"description":2926,"labels":2927,"number":2929,"owner":2872,"repository":2873,"state":2902,"title":2930,"updated_at":2931,"url":2932,"score":2933},"#877 did introduce an regression (I did also not notice while reviewing :/ ) \r\n\r\nWP only exec 1 pipeline but should do 2\r\n\r\n## Before\r\nhttps://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/2558\r\n## Now :/\r\nhttps://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/2563",[2928],{"name":2866,"color":2867},931,"Pipelines are skipped where they should not","2022-05-20T03:37:11Z","https://github.com/woodpecker-ci/woodpecker/issues/931",0.7652076,{"description":2935,"labels":2936,"number":2938,"owner":2872,"repository":2873,"state":2902,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Clear and concise description of the problem\r\n\r\nI would like to pick a deployment environment from a list when pressing the deploy button, instead of having to type it in.\r\n\r\n### Suggested solution\r\n\r\n* In the \"Deploy\" dialog, allow picking \"Target deployment environment\" from a list of all environments listed in the pipeline\r\n\r\n### Alternative\r\n\r\n* On the repository settings page, add a \"Deployment environments\" input, for a \"Comma-separated list of deployment environments\"\r\n* In the \"Deploy\" dialog, allow picking an option from the environments listed in the settings. \r\n\r\n### Additional context\r\n\r\nI only have a single environment anyway, so needing to remember/look up what I called it and type that in feels kind of pointless.\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/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 request the same feature to avoid creating a duplicate.",[2937],{"name":2912,"color":2913},2067,"Deploy dialog: pick environment from a list","2023-08-08T11:23:13Z","https://github.com/woodpecker-ci/woodpecker/issues/2067",0.76566166,{"description":2944,"labels":2945,"number":2947,"owner":2872,"repository":2873,"state":2902,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Clear and concise description of the problem\n\nsometimes one may want to debug pipelines, which may involve printing sensitive info.\r\nnow, one may fortunately set such a repo to private to protect such info, but ideally, one would be able to cleanse any such sensitive info such as to put such a repo public again.\n\n### Suggested solution\n\nallow deleting runs to cleanse sensitive info\n\n### Alternative\n\nkeep repo private to protect sensitive info\n\n### Additional context\n\nversion: next\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.",[2946],{"name":2912,"color":2913},1883,"allow deleting runs","2023-07-01T07:18:55Z","https://github.com/woodpecker-ci/woodpecker/issues/1883",0.7728851,{"description":2953,"labels":2954,"number":2957,"owner":2872,"repository":2873,"state":2902,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Component\n\nweb-ui\n\n### Describe the bug\n\npipeline file like this\r\n\r\n```yml\r\n---\r\nlabels:\r\n platform: linux/amd64\r\n backend: local\r\n\r\nsteps:\r\n hello:\r\n image: bash\r\n commands:\r\n - uname -a\r\n - pwd\r\n - ls -AFlh\r\n - echo \"hello world 你好\"\r\n - touch hello.txt\r\n - echo $${PATH}\r\n\r\n 测试:\r\n image: bash\r\n commands:\r\n - uname -a\r\n - pwd\r\n - ls -AFlh\r\n - echo \"hello world 你好 测试\"\r\n\r\n```\r\n\r\nbut display wrong in webui\r\n\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"1.0.3\"}\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/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).",[2955,2956],{"name":2866,"color":2867},{"name":2896,"color":2897},2609,"pipeline config display utf-8 character wrong","2024-01-03T09:39:05Z","https://github.com/woodpecker-ci/woodpecker/issues/2609",0.77293277,{"description":2963,"labels":2964,"number":2966,"owner":2872,"repository":2873,"state":2902,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nSince https://github.com/woodpecker-ci/woodpecker/issues/1948 was fixed (yesterday), the json schema for `.woodpecker.yml` is out of date, but that issue was locked so I can't comment there.\r\n\r\nThis is possible so that the logs show \"clone\" (as it was before the fix) instead of \"git\":\r\n```yml\r\nclone:\r\n clone: # can be any word: \"clone\", \"git\" or whatever\r\n image: woodpeckerci/plugin-git:2.0.3\r\nsteps:\r\n build:\r\n # ...\r\n```\r\nBut the schema [only allows `\"git\"`](https://github.com/woodpecker-ci/woodpecker/blob/3a85559763a5a9df197ffc04a4c22294ccf5097b/pipeline/schema/schema.json#L45). If I use `\"clone\"` then I get an error in vscode: `Property clone is not allowed.`.\r\n\r\nI couldn't submit a PR because I'm unsure how to fix it - I can't just change \"git\" to \"clone\" as both are valid, as well as any other word.\r\n\r\n(I'm willing to try fixing it if someone has an idea how to specify \"any word\"?)\r\n\r\n### System Info\r\n\r\n```shell\r\nversion next\r\nvscode\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).",[2965],{"name":2866,"color":2867},2020,"JSON schema out of date","2023-08-03T13:50:11Z","https://github.com/woodpecker-ci/woodpecker/issues/2020",0.7748583,{"description":2972,"labels":2973,"number":2975,"owner":2872,"repository":2873,"state":2902,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nThe code contains the inline styles.\r\nInline style, seems, was only in `web/src/components/admin/settings/queue/AdminQueueStats.vue:25` before.\r\n\r\n### Expected behavior\r\n\r\nShould not be inline styles.\r\n\r\nhttps://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/style\r\nhttps://stackoverflow.com/questions/2612483/whats-so-bad-about-in-line-css\r\nhttps://content-security-policy.com/unsafe-inline/\r\n\r\n### System Info\r\n\r\n`next`\r\n\r\n### Additional context\r\n\r\nI accidentally saw #4609 and wanted to comment there, but I'm not allowed to comment on `pat-s` issues and PRs.\r\n\r\n### Validations\r\n\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]",[2974],{"name":2866,"color":2867},4616,"Inline styles","2024-12-27T23:10:03Z","https://github.com/woodpecker-ci/woodpecker/issues/4616",0.7775963,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fescj8GTWGYH5Pu0QTcxiS5_FGuaAR0YGBUVRHcp-DeE":-1},"/woodpecker-ci/woodpecker/1345"]