\n\n### Steps to reproduce\n\nFirst pipeline is `quality.yml` :\n\n```yaml\nwhen:\n - event: push\n branch: master\n - event: pull_request\n\nskip_clone: true\n\nsteps:\n- name: clone\n image: bitnami/git:latest\n pull: true\n environment:\n # hidden\n commands:\n # hidden\n# other steps (install, lint, test)\n```\n\nSecond pipeline is `build.yml` :\n\n```yaml\nwhen:\n - event: tag\n\nskip_clone: true\n\nsteps:\n- name: clone\n image: bitnami/git:latest\n pull: true\n environment:\n # hidden\n commands:\n # hidden\n- name: docker \n image: woodpeckerci/plugin-docker-buildx:latest\n pull: true\n settings:\n # hidden\n```\n\nCommand to trigger on the repository is `git push && git push --tags`\n\n### Expected behavior\n\nBoth pipelines should run at the same time without cancelling each other.\n\n### System Info\n\n```shell\nWoodpecker runs on Docker, latest version (3.10) on a Debian system up to date.\n\nNon-secret server environment variables :\n\n\nWOODPECKER_MAX_WORKFLOWS=2\nWOODPECKER_BACKEND=docker\nWOODPECKER_PLUGINS_PRIVILEGED=woodpeckerci/plugin-docker-buildx\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]",[3184],{"name":3185,"color":3186},"bug","d73a4a",5581,"woodpecker-ci","woodpecker","open","Different event gets cancelled","2025-09-30T14:56:19Z","https://github.com/woodpecker-ci/woodpecker/issues/5581",0.6610981,{"description":3196,"labels":3197,"number":3199,"owner":3188,"repository":3189,"state":3190,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nStep with `when.status: [failure]` doesn't run on failed pipeline, instead runs step with `when.status: [success]`.\r\n\r\n### Steps to reproduce\r\n\r\n1. Woodpecker + some Forge\r\n2. Make a pipeline\r\n\r\n```yaml\r\n# build.yaml\r\nskip_clone: true\r\nsteps:\r\n build:\r\n image: alpine\r\n commands:\r\n - echo 'Building the app'\r\n - exit 1 # 0 - success, 1 - fail\r\n```\r\n```yaml\r\n# notifications.yaml\r\nskip_clone: true\r\ndepends_on: [build]\r\nruns_on: [success, failure]\r\nsteps:\r\n fail-notification:\r\n when:\r\n - status: [failure]\r\n image: alpine\r\n commands:\r\n - echo 'Build failed'\r\n success-notification:\r\n when:\r\n - status: [success]\r\n image: alpine\r\n commands:\r\n - echo 'Build succeed'\r\n```\r\n3. Run manually and get wrong step execution\r\n\r\n\r\n### Expected behavior\r\n\r\n1. `fail-notification` step runs\r\n2. `success-notification` skips\r\n\r\n### System Info\r\n\r\n```shell\r\nWP `next-f87e80381b`, `2.7.1`, Gitea, Postgres 16\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/issues/4337#issuecomment-2468498847\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]",[3198],{"name":3185,"color":3186},4355,"when.status:failure doesn't work across workflows (runs_on:failure)","2024-11-19T10:27:03Z","https://github.com/woodpecker-ci/woodpecker/issues/4355",0.6847608,{"description":3205,"labels":3206,"number":3207,"owner":3188,"repository":3189,"state":3208,"title":3209,"updated_at":3210,"url":3211,"score":3212},"### Clear and concise description of the problem\n\nI am trying to setup a pipeline with several steps, the last two should fire depending on the tag\r\n\r\nif the tag follows the pattern vX.X.X i want to execute step A\r\nIf the tag follows vX.X.X-preXX i want to execute step B\r\n\r\nHow can I set this up ? \r\n\r\nYet another issue I ran into was: How can I make a whole pipeline only run on tags ? and disable pushes ?\r\nCurrently I have a event condition on all steps, but it will still trigger the clone step everytime, also it is kinda not elegant to have this condition on all steps, I would prefer a global condition like the one for branches\r\n\r\nam I missing something or is this a little more complicated ?\n\n### Suggested solution\n\nWhen we find a solution I would update the docs with an example, I think this usecase is not uncommon\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.",[],961,"closed","Exclude condition for tag pattern","2022-12-23T19:30:49Z","https://github.com/woodpecker-ci/woodpecker/issues/961",0.63649184,{"description":3214,"labels":3215,"number":3220,"owner":3188,"repository":3189,"state":3208,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Component\n\nserver\n\n### Describe the bug\n\nIf the last commit in e.g. the main branch has `skip ci` in its commit message, creating a tag on top of that commit does not trigger the CI as it results in an empty pipeline.\n\n### System Info\n\n```shell\nversion\t\"next-6a6cb094fb\"\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]",[3216,3217],{"name":3185,"color":3186},{"name":3218,"color":3219},"forge/github","E96280",3606,"Tagging not working if last commit in target branch has \"skip ci\"","2024-04-14T12:25:29Z","https://github.com/woodpecker-ci/woodpecker/issues/3606",0.6567018,{"description":3226,"labels":3227,"number":3228,"owner":3188,"repository":3189,"state":3208,"title":3229,"updated_at":3230,"url":3231,"score":3232},"When I tag/release two builds are executed. One of them does the `when: event: tag` part and the other does not. I think this is because one of the builds is executed because Woodpecker sees a new branch.\r\n\r\n\r\n\r\nWeirdly enough, if I add a `branches: master` the build will time out saying exit code 0 on all steps without any further info from the step execution. [Might be a separate issue]\r\n\r\nMy `.drone.yml`:\r\n```\r\npipeline:\r\n build:\r\n image: debian\r\n pull: true\r\n commands:\r\n - echo \"HALLO WELT, KANNST DU MICH HOEREN\"\r\n when:\r\n event: [push, tag]\r\n\r\n package:\r\n image: debian\r\n pull: true\r\n commands:\r\n - echo \"zap\"\r\n when:\r\n event: tag\r\n\r\n# Not working :/\r\n#branches: master\r\n```\r\n\r\nI am using Gitea as my VCS and have enabled all 4 webhook triggers in the settings.",[],274,"Duplicate pipeline execution on tag event","2021-08-31T01:00:29Z","https://github.com/woodpecker-ci/woodpecker/issues/274",0.6650066,{"description":3234,"labels":3235,"number":3237,"owner":3188,"repository":3189,"state":3208,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe pipeline status image (on Woodpecker - returned by API: /api/badges/25/status.svg ) shows ERROR, even that last build is OK:\r\n\r\n\n\n### System Info\n\n```shell\nversion 2.4.1 running on Docker\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]",[3236],{"name":3185,"color":3186},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.6764504,{"description":3243,"labels":3244,"number":3249,"owner":3188,"repository":3189,"state":3208,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Component\n\nserver\n\n### Describe the bug\n\nSometimes pipeline cancellations still result in errors that will flag the pipeline as failed instead of cancelled:\r\n\r\n\r\n\n\n### Steps to reproduce\n\nHave not found a reliable way to reproduce this specific case.\n\n### Expected behavior\n\nPipeline should be marked as cancelled instead of failed.\n\n### System Info\n\n```shell\nnext-bf5405b6cc\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]",[3245,3246],{"name":3185,"color":3186},{"name":3247,"color":3248},"ui","46DEA2",4349,"Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.67871016,{"description":3255,"labels":3256,"number":3257,"owner":3188,"repository":3189,"state":3208,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### Component\n\ncli\n\n### Describe the bug\n\nSame as in #1379, found while fixing that part of the schema.json.\r\n\r\nTag in the schema currently only supports a string while the pipeline/frontend/yaml/constraints/constraints.go also accepts an array of strings.\n\n### System Info\n\n```shell\nv0.15.4 (problem is existent on the release/v0.15 branch, so all v0.15s at least, fixed by the large rewrite applied to main)\n```\n\n\n### Additional context\n\nI'll head in and fix this as well...\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) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[],1381,"Conditional pipeline.step.when.tag not taking array as documented in 0.15","2022-11-05T00:04:12Z","https://github.com/woodpecker-ci/woodpecker/issues/1381",0.6790002,{"description":3263,"labels":3264,"number":3267,"owner":3188,"repository":3189,"state":3208,"title":3268,"updated_at":3269,"url":3270,"score":3271},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nhttps://github.com/user-attachments/assets/ae56c58f-717b-4915-aad3-effdd9640fe2\r\n\r\nSometimes `pipeline.` is rendered instead of the commit hash. I guess that's a race condition during data loading from pinia. What I'm wondering about it, this only happens while a user is logged in. If the pipeline list is loaded as unauthenticated, everything seems to be working as intended.\r\n\r\n### Steps to reproduce\r\n\r\nReload the pipeline list multiple times.\r\n\r\n### Expected behavior\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-d0e4a176f1\"}\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]",[3265,3266],{"name":3185,"color":3186},{"name":3247,"color":3248},4537,"Race condition while rendering pipeline commit","2025-01-19T21:42:00Z","https://github.com/woodpecker-ci/woodpecker/issues/4537",0.68279094,{"description":3273,"labels":3274,"number":3276,"owner":3188,"repository":3189,"state":3208,"title":3277,"updated_at":3278,"url":3279,"score":3280},"### Component\n\nserver\n\n### Describe the bug\n\nCurrently even if global when is set warning for each step is still shown\r\n```\r\n[bad_habit] Please set an event filter on all when branches\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-65d88be523\"}\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]",[3275],{"name":3185,"color":3186},3401,"Linter should not report warning for missing when in steps if global when is set","2024-04-02T08:10:25Z","https://github.com/woodpecker-ci/woodpecker/issues/3401",0.6855966,["Reactive",3282],{},["Set"],["ShallowReactive",3285],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fP91B4XeZ2l6wpFtsy2d83xQZ8Pzav0bYVojMh6PqVA8":-1},"/woodpecker-ci/woodpecker/894"]