\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]",[2012,2013],{"name":1999,"color":2000},{"name":2014,"color":2015},"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.770507,{"description":2022,"labels":2023,"number":2028,"owner":1988,"repository":1989,"state":1990,"title":2029,"updated_at":2030,"url":2031,"score":2032},"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",[2024,2025],{"name":1985,"color":1986},{"name":2026,"color":2027},"build","6AB8BA",3087,"build: delete pr images on pull close","2023-12-31T07:28:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3087",0.7763667,{"description":2034,"labels":2035,"number":2038,"owner":1988,"repository":1989,"state":1990,"title":2039,"updated_at":2040,"url":2041,"score":2042},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[2036,2037],{"name":1999,"color":2000},{"name":2002,"color":2003},4249,"[Bug] MultiForge: second forge can not be used","2024-10-25T17:33:00Z","https://github.com/woodpecker-ci/woodpecker/issues/4249",0.77858555,{"description":2044,"labels":2045,"number":2048,"owner":1988,"repository":1989,"state":1990,"title":2049,"updated_at":2050,"url":2051,"score":2052},"ERROR: `{\"level\":\"error\",\"time\":\"2023-09-07T13:31:07Z\",\"message\":\"cannot verify team membership for .\"}`\r\n\r\n### Discussed in https://github.com/woodpecker-ci/woodpecker/discussions/2377\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **pat-s** September 7, 2023\u003C/sup>\r\nWhen this message appears in the logs, a member is not being able to login but instead pushed back to the log screen again without further information. \u003C/div>\n\n(You're unable to login because of registration restrictions to specific orgs with `WOODPECKER_ORGS` -> show this to users)",[2046,2047],{"name":2014,"color":2015},{"name":1985,"color":1986},2442,"Show to user if you're not allowed to login without correct org membership","2023-09-17T07:05:04Z","https://github.com/woodpecker-ci/woodpecker/issues/2442",0.78047204,{"description":2054,"labels":2055,"number":2057,"owner":1988,"repository":1989,"state":2058,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### 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).",[2056],{"name":1999,"color":2000},1871,"closed","Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.7612304,{"description":2064,"labels":2065,"number":2070,"owner":1988,"repository":1989,"state":2058,"title":2071,"updated_at":2072,"url":2073,"score":2074},"### Clear and concise description of the problem\n\nWhen committing with a structured message (e.g. following Conventional Commits specification), Woodpecker cramps the whole message together into one large string when displaying it in the repo commit list and the pipeline run title. This is usually pretty ugly and decreases readability. \r\n\r\nExample:\r\n\r\n\n\n### Suggested solution\n\nA new environment variable CI_COMMIT_MESSAGE_HEADER could be added which would be used to populate the strings mentioned above. This would of course require parsing the commit message first.\n\n### Alternative\n\nAlternatively, a UI section for the body and footer of the commit message could be added below the pipeline run title to display those variables. \r\n\r\nAll of the steps described above would still be necessary, but in addition, at least CI_COMMIT_MESSAGE_BODY (if one wants to treat body and footer as one) would have to be parsed and added as well.\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.",[2066,2067],{"name":2014,"color":2015},{"name":2068,"color":2069},"feature","180DBE",1489,"Beautify display of commit messages with bodies and/or footers","2023-08-20T16:52:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1489",0.76370335,{"description":2076,"labels":2077,"number":2079,"owner":1988,"repository":1989,"state":2058,"title":2080,"updated_at":2081,"url":2082,"score":2083},"### Component\n\nserver\n\n### Describe the bug\n\nTrying out woodpecker, my docker-compose file:\n```\nservices:\n woodpecker-server:\n image: woodpeckerci/woodpecker-server:v3\n ports:\n - 8000:8000\n volumes:\n - woodpecker-server-data:/var/lib/woodpecker/\n environment:\n - WOODPECKER_OPEN=true\n - WOODPECKER_HOST=http://192.168.10.162:8000\n\nvolumes:\n woodpecker-server-data:\n```\n\nWhen running with `docker compose up`, I get the following:\n```\n~/projects/foss/woodpecker$ docker compose up\n[+] Running 1/1\n ✔ Container woodpecker-woodpecker-server-1 Created 0.1s \nAttaching to woodpecker-server-1\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"log level: info\"}\nwoodpecker-server-1 | {\"level\":\"warn\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"no sqlite3 file found, will create one at '/var/lib/woodpecker/woodpecker.sqlite'\"}\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"can't setup store: could not migrate datastore: unable to open database file: no such file or directory\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"error running server\"}\nwoodpecker-server-1 exited with code 0\n~/projects/foss/woodpecker$ \n```\n\nAlso, I doubled checked the volume dir, and there is no files there:\n```\nroot@[REDACTED]:/var/lib/docker/volumes/woodpecker_woodpecker-server-data/_data# ls -la\ntotal 0\ndrwxr-xr-x. 1 root root 0 Mar 5 04:50 .\ndrwx-----x. 1 root root 10 Mar 7 18:37 ..\nroot@[REDACTED]:/var/lib/docker/volumes/woodpecker_woodpecker-server-data/_data# \n```\n\n\n### Steps to reproduce\n\n1. Woodperker with docker (configuration from docs) & agent entry removed. (only service)\n2. `docker compose up`\n3. Observe the error\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nDocker version 28.0.1, build 068a01e\n```\n\n### Additional context\n\n**However**, when running with `woodpeckerci/woodpecker-server:v3-alpine` image - this issue goes away.\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]",[2078],{"name":1999,"color":2000},4939,"Fresh run with docker results in \"unable to open database file\"","2025-03-18T16:47:23Z","https://github.com/woodpecker-ci/woodpecker/issues/4939",0.7675774,{"description":2085,"labels":2086,"number":2088,"owner":1988,"repository":1989,"state":2058,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### 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.",[2087],{"name":2068,"color":2069},946,"Global defaults for some keywords","2023-08-20T20:29:48Z","https://github.com/woodpecker-ci/woodpecker/issues/946",0.7685146,["Reactive",2094],{},["Set"],["ShallowReactive",2097],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"qjI8s80ak9KAS0NMZGrTxPJoKKxGtgOL9NcGoApGDpY":-1},"/woodpecker-ci/woodpecker/3870"]