\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]",[3196,3199],{"name":3197,"color":3198},"bug","d73a4a",{"name":3200,"color":3201},"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.7391355,{"description":3211,"labels":3212,"number":3213,"owner":3203,"repository":3204,"state":3205,"title":3214,"updated_at":3215,"url":3216,"score":3217},"we should probably have some way to either dedublicate the error and use the key at the bottom that caused it or make it hirachcial\n\n\u003Cimg width=\"1360\" height=\"352\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/95a62a2c-4f04-4874-be21-40196a45b5df\" />\n\nis actually not 3 but one single issue",[],5568,"[UX] config linter passes jsonSchema errors throug even if redundant","2025-09-29T13:54:25Z","https://github.com/woodpecker-ci/woodpecker/issues/5568",0.76540715,{"description":3219,"labels":3220,"number":3224,"owner":3203,"repository":3204,"state":3205,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### Component\n\nserver\n\n### Describe the bug\n\nWhile testing the ntfy plugin to send notifications after pipeline failure I wanted to use `CI_STEP_NAME` but it doesn't return a value. The other CI_STEP_* variables are not returning anything either.\r\n\r\nHere a example pipeline. I have added `CI_WORKFLOW_NAME` which does work.\r\n```\r\npipeline:\r\n deploy:\r\n image: alpine:latest\r\n commands:\r\n - exit 1\r\n\r\n notify_on_failure:\r\n image: codeberg.org/l-x/woodpecker-ntfy\r\n settings:\r\n url: https://ntfy.example.com/ci\r\n token:\r\n from_secret: ntfy_token\r\n title: Build failure\r\n priority: urgent\r\n icon: https://woodpecker-ci.org/img/logo.svg\r\n tags: x, robot\r\n message: >\r\n Workflow: ${CI_WORKFLOW_NAME}\r\n Step name: ${CI_STEP_NAME}\r\n Step status: ${CI_STEP_STATUS}\r\n Step started: ${CI_STEP_STARTED}\r\n Step finished: ${CI_STEP_FINISHED}\r\n when:\r\n status: [ failure ]\r\n```\n\n### System Info\n\n```shell\nVersion: next-02913fa7\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] 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).",[3221],{"name":3222,"color":3223},"enhancement","7E1FE4",1760,"`CI_STEP_*` environment variables do not return values","2024-10-05T23:54:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1760",0.7665433,{"description":3230,"labels":3231,"number":3236,"owner":3203,"repository":3204,"state":3237,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Component\n\nagent\n\n### Describe the bug\n\nAgent image builds with `next-*` version instead of tag/release. Server version is OK.\n\n### System Info\n\n```shell\n{\"level\":\"info\",\"time\":\"2023-08-17T11:47:41Z\",\"message\":\"Starting Woodpecker server with version '1.0.2'\"}\r\n{\"level\":\"info\",\"time\":\"2023-08-17T12:01:26Z\",\"message\":\"Starting Woodpecker agent with version 'next-d9e06696' and backend 'kubernetes' using platform 'linux/amd64' running up to 1 pipelines in parallel\"}\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).",[3232,3233],{"name":3197,"color":3198},{"name":3234,"color":3235},"build","6AB8BA",2236,"closed","Incorrect version of agent","2023-08-18T14:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2236",0.72077346,{"description":3243,"labels":3244,"number":3246,"owner":3203,"repository":3204,"state":3237,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### 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).",[3245],{"name":3197,"color":3198},2020,"JSON schema out of date","2023-08-03T13:50:11Z","https://github.com/woodpecker-ci/woodpecker/issues/2020",0.7315648,{"description":3252,"labels":3253,"number":3255,"owner":3203,"repository":3204,"state":3237,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### 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).",[3254],{"name":3197,"color":3198},1871,"Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.7338934,{"description":3261,"labels":3262,"number":3264,"owner":3203,"repository":3204,"state":3237,"title":3265,"updated_at":3266,"url":3267,"score":3268},"### Component\n\nserver, web-ui\n\n### Describe the bug\n\nJust open Chrome developer tools window and navigate to https://ci.woodpecker-ci.org.\r\n\r\nerror message\r\n`Refused to apply style from 'https://ci.woodpecker-ci.org/assets/custom.css' because its MIME type ('text/plain') is not a supported stylesheet MIME type, and strict MIME checking is enabled.`\r\n\r\n\r\n\n\n### System Info\n\n```shell\n* Chrome latest version (as of 2023-10-01)\r\n* Woodpecker next-7d2bf54685\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).",[3263],{"name":3197,"color":3198},2514,"when no custom css/js is defined, wrong mimetype causes Chrome to complain","2023-10-03T10:28:22Z","https://github.com/woodpecker-ci/woodpecker/issues/2514",0.73647505,{"description":3270,"labels":3271,"number":3273,"owner":3203,"repository":3204,"state":3237,"title":3274,"updated_at":3275,"url":3276,"score":3277},"### Component\r\n\r\nserver, web-ui\r\n\r\n### Describe the bug\r\n\r\nHi, I have problem with my woodpecker instance. I'm using Github to provide OAuth2 Authorization. But the problem I cannot log in to the app. When I clicking \"Log in\" button, it returns to the same screen. Sometimes when I do many clicks in small amount time I need reatuhorize it in Github.\r\n\r\nInstance is hidden with ngnix proxy manager. \r\n\r\nMy docker compose looks like this:\r\n```\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n expose:\r\n - 8000\r\n - 9000\r\n volumes:\r\n - ./woodpecker-server-data:/var/lib/woodpecker/\r\n environment:\r\n - WOODPECKER_OPEN=false\r\n - WOODPECKER_HOST=${WOODPECKER_HOST}\r\n - WOODPECKER_GITHUB=true\r\n - WOODPECKER_GITHUB_CLIENT=${WOODPECKER_GITHUB_CLIENT}\r\n - WOODPECKER_GITHUB_SECRET=${WOODPECKER_GITHUB_SECRET}\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_ADMIN=${WOODPECKER_ADMIN}\r\n - WOODPECKER_REPO_OWNERS=${WOODPECKER_REPO_OWNERS}\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:latest\r\n command: agent\r\n restart: always\r\n depends_on:\r\n - woodpecker-server\r\n volumes:\r\n - ./woodpecker-agent-config:/etc/woodpecker\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n environment:\r\n - WOODPECKER_SERVER=woodpecker-server:9000\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_BACKEND_DOCKER_NETWORK=composehook-internal\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\nnetworks:\r\n ngnix-internal:\r\n external: true\r\n name: ngnix-internal\r\n composehook-internal:\r\n external: true\r\n name: composehook-internal\r\n```\r\n\r\nIn logs I haven't see something weird or wrong.\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\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 [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]",[3272],{"name":3197,"color":3198},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.74543756,{"description":3279,"labels":3280,"number":3284,"owner":3203,"repository":3204,"state":3237,"title":3285,"updated_at":3286,"url":3287,"score":3288},"### 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.",[3281],{"name":3282,"color":3283},"feature","180DBE",1883,"allow deleting runs","2023-07-01T07:18:55Z","https://github.com/woodpecker-ci/woodpecker/issues/1883",0.7513206,{"description":3290,"labels":3291,"number":3293,"owner":3203,"repository":3204,"state":3237,"title":3294,"updated_at":3295,"url":3296,"score":3297},"### Component\n\nagent\n\n### Describe the bug\n\nBy default netrc credentials (i.e. git credentials) are not injected into builds unless\r\n\r\n- the repo is set to trusted (which can only be done by admins)\r\n- \"Only inject netrc credentials into trusted containers\" is unchecked\r\n\r\nHowever, the latter does not work as executing a \"git push\" back to the checked out repo does not work when **the option is unchecked**.\r\nIt only works if the repo is set to \"trusted\" - which cannot be enabled by a normal user.\r\n\r\nShowcasing this in an example repo is hard as normal users cannot open the settings of a repo.\r\nI've tested this multiple times in an example repo toggling different options on and off and running a simple `git push` at the end (after a dummy modification).\r\n\r\nAlso I think the current docs are wrong\r\n\r\n> Cloning pipeline step may need git credentials. They are injected via netrc. By default, they're only injected if this option is enabled, the repo is trusted ([see above](#trusted)) or the image is a trusted clone image. If you uncheck the option, git credentials will be injected into any container in clone step.\r\n\r\nI think it should read as:\r\n\r\n\"By default, they're only injected if this option is enabled **and** the repo is trusted - or if the \"inject\" option is unchecked.\"\r\n\r\nAlso \"git credentials will be injected into any container in clone step\" -> should probably be \"into any container **in addition** to the 'clone' step\". \n\n### System Info\n\n```shell\n`next-8629a418f8`\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).",[3292],{"name":3222,"color":3223},2583,"Injecting netrc credentials into non-trusted containers does not work","2024-11-10T15:42:36Z","https://github.com/woodpecker-ci/woodpecker/issues/2583",0.754125,["Reactive",3299],{},["Set"],["ShallowReactive",3302],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fxQX3mCFPSa9gEDsCJgU4UHC9RJMmv6GNxDZTv9a0GAM":-1},"/woodpecker-ci/woodpecker/3998"]