\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,2883],{"name":2866,"color":2867},{"name":2884,"color":2885},"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.7463297,{"description":2892,"labels":2893,"number":2900,"owner":2872,"repository":2873,"state":2874,"title":2901,"updated_at":2902,"url":2903,"score":2904},"we currently don't have a concept how to translate/interpreter the services into \"local backend\" and just ignore them.\r\n\r\nwe should have it that way so it works very similar to what the user know with docker or kube backend.",[2894,2897],{"name":2895,"color":2896},"enhancement","7E1FE4",{"name":2898,"color":2899},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.7524316,{"description":2906,"labels":2907,"number":2910,"owner":2872,"repository":2873,"state":2874,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Component\n\nweb-ui\n\n### Describe the bug\n\nText parsing of an http link printed in color on the output console adds a span tag to the HTML\n\n\n\n### Steps to reproduce\n\n- Example pipeline\n\n```yaml\n - name: test\n image: alpine:3.21\n commands:\n - NOCOLOR='\\\\033[0m'\n - BLUE='\\\\033[0;34m'\n - echo -e \"$${BLUE}https://docs.astral.sh/ruff/rules/pytest-fixture-positional-args/$${NOCOLOR}\"\n - echo \"https://docs.astral.sh/ruff/rules/pytest-fixture-positional-args\"\n```\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\nsource: \"https://github.com/woodpecker-ci/woodpecker\",\nversion: \"3.0.1\"\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/versions]",[2908,2909],{"name":2866,"color":2867},{"name":2884,"color":2885},4907,"Console parsing input text for colored html link","2025-03-14T13:19:12Z","https://github.com/woodpecker-ci/woodpecker/issues/4907",0.7567333,{"description":2916,"labels":2917,"number":2922,"owner":2872,"repository":2873,"state":2874,"title":2923,"updated_at":2924,"url":2925,"score":2926},"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- [ ] ...",[2918,2921],{"name":2919,"color":2920},"tests","ACEA1E",{"name":2869,"color":2870},3819,"Create \"backend integration test\" framework","2024-11-05T23:18:48Z","https://github.com/woodpecker-ci/woodpecker/issues/3819",0.7577285,{"description":2928,"labels":2929,"number":2933,"owner":2872,"repository":2873,"state":2934,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### 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.",[2930,2931],{"name":2895,"color":2896},{"name":2932,"color":2899},"backend/kubernetes",3473,"closed","Support for setting runtime class on Kubernetes backend","2024-03-29T09:29:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3473",0.6943844,{"description":2940,"labels":2941,"number":2943,"owner":2872,"repository":2873,"state":2934,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### 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]",[2942],{"name":2866,"color":2867},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.7159709,{"description":2949,"labels":2950,"number":2955,"owner":2872,"repository":2873,"state":2934,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Component\n\nserver\n\n### Describe the bug\n\nWe like to setup a workflow that is skipped if a change contains ONLY changes to a certain list of files. For that we tried using a `when` condition similar to this:\n\n```yaml\nwhen:\n - event: pull_request\n path:\n exclude: [ 'README.md' ]\n include: [ 'src/*.go' ]\n```\n\nThis will however make woodpecker skip the workflow for any commit that touches files listed in `exclude`. Including commits that change other files in addition. E.g. if I have a commit changing `src/main.go` and `README.md` the workflow will not be executed.\nIs that really the desired behavior? To me it looks more like a but. I could be wrong, but I would expect the more common use case for such an `exclude` constraint to be to skip execution when an change contains only files that are listed in `exclude` and to not skip as soon as at least one file is changed that is not excluded.\n\n### Steps to reproduce\n\n- Create a woodpecker workflow with the above `path` constraint. \n- Submit a change that touches `README.md` and `src/main.go` \n- The workflow will not be executed\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nwoodpecker v3.4.x, happens also on the current main branch\n```\n\n### Additional context\n\nI'll try to submit a PR with adjusted unit tests to clarify what I think is the more useful behavior.\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]",[2951,2952],{"name":2866,"color":2867},{"name":2953,"color":2954},"pipeline-config","1BE540",5041,"Weird behavior on path exclude contraints","2025-04-01T18:05:53Z","https://github.com/woodpecker-ci/woodpecker/issues/5041",0.7162838,{"description":2961,"labels":2962,"number":2964,"owner":2872,"repository":2873,"state":2934,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### 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).",[2963],{"name":2866,"color":2867},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.72014153,{"description":2970,"labels":2971,"number":2975,"owner":2872,"repository":2873,"state":2934,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### Clear and concise description of the problem\r\n\r\n`Woodpecker CI` could benefit from using some defaults to avoid repetitive blocks and/or references to anchors.\r\n\r\nThis is something I used to use in `GitLab CI` and it makes the pipeline really compact. For instance, they have a `default` keyword to configure some \"default\" values that apply to all subsequent steps — when relevant.\r\n\r\n### Suggested solution\r\n\r\n```yaml\r\ndefault:\r\n image: docker.io/library/rust:1.61-slim-bullseye\r\n\r\npipeline:\r\n format:\r\n commands:\r\n - rustup component add rustfmt\r\n - cargo fmt -- --check\r\n environment:\r\n CARGO_HOME: .cargo/\r\n group: verify\r\n # No need to specify image here since it's inferred by \"default\"\r\n assemble:\r\n commands:\r\n - cargo build\r\n environment:\r\n CARGO_HOME: .cargo/\r\n group: assemble\r\n # No need to specify image here since it's inferred by \"default\"\r\n publish:\r\n commands:\r\n - cargo blah\r\n environment:\r\n CARGO_HOME: .cargo/\r\n group: publish\r\n image: docker.io/library/rust:1.62-slim-bullseye # ...if defined, overwrites what's in default\r\n```\r\n\r\n### Alternative\r\n\r\nYAML aliases and anchors :unamused:\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 request the same feature to avoid creating a duplicate.",[2972],{"name":2973,"color":2974},"feature","180DBE",946,"Global defaults for some keywords","2023-08-20T20:29:48Z","https://github.com/woodpecker-ci/woodpecker/issues/946",0.73270476,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMVbc_gRkPRTssQUth6c0ckVlusCsH7x8O2Uutj9w-Xw":-1},"/woodpecker-ci/woodpecker/1760"]