\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]",[2879,2880],{"name":2866,"color":2867},{"name":2881,"color":2882},"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.75218123,{"description":2889,"labels":2890,"number":2897,"owner":2869,"repository":2870,"state":2871,"title":2898,"updated_at":2899,"url":2900,"score":2901},"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.",[2891,2894],{"name":2892,"color":2893},"enhancement","7E1FE4",{"name":2895,"color":2896},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.75384855,{"description":2903,"labels":2904,"number":2908,"owner":2869,"repository":2870,"state":2871,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### Clear and concise description of the problem\r\n\r\nFor build steps, I might be fine with using a \":latest\" image, but for diagnostics I want to be able to see exactly which image was used for a build. \r\n\r\n### Suggested solution\r\n\r\nPrint the docker image hash as a log line\r\n\r\n### Alternative\r\n\r\n_No response_\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.",[2905],{"name":2906,"color":2907},"feature","180DBE",1414,"record build step docker image id","2023-08-20T17:13:01Z","https://github.com/woodpecker-ci/woodpecker/issues/1414",0.75407046,{"description":2914,"labels":2915,"number":2918,"owner":2869,"repository":2870,"state":2871,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Clear and concise description of the problem\n\nWhen following the logs of a step I would like the UI to automatically select the next step if the step I am currently looking at has finished.\n\n### Suggested solution\n\nAutomatically jump to the next step when currently visible step status changes to successfully finished.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\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 [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.",[2916,2917],{"name":2881,"color":2882},{"name":2892,"color":2893},3801,"Log jump to next step when finished","2024-06-24T11:59:39Z","https://github.com/woodpecker-ci/woodpecker/issues/3801",0.7645263,{"description":2924,"labels":2925,"number":2933,"owner":2869,"repository":2870,"state":2934,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Component\n\nother\n\n### Describe the bug\n\nI tried to use the Gitpop linked in the Readme, but it doesn't work. Seems like the Go Version is to old.\n\n### System Info\n\n```shell\nNone\n```\n\n\n### Additional context\n\nThe log:\r\n```\r\n HISTFILE=/workspace/.gitpod/cmd-4 history -r; {\r\ncd docs/\r\n\r\n} && {\r\npnpm install\r\npnpm build:woodpecker-plugins\r\n\r\n} && {\r\npnpm start --port 4000\r\n\r\n}\r\ngitpod /workspace/woodpecker (master) $ HISTFILE=/workspace/.gitpod/cmd-4 history -r; {\r\n> cd docs/\r\n> \r\n> } && {\r\n> pnpm install\r\n> pnpm build:woodpecker-plugins\r\n> \r\n> } && {\r\n> pnpm start --port 4000\r\n> \r\n> }\r\nScope: all 2 workspace projects\r\nLockfile is up to date, resolution step is skipped\r\nPackages: +1137\r\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\n\r\n ╭─────────────────────────────────────────────────────────────────╮\r\n │ │\r\n │ Update available! 8.3.1 → 8.6.5. │\r\n │ Changelog: https://github.com/pnpm/pnpm/releases/tag/v8.6.5 │\r\n │ Run \"pnpm add -g pnpm\" to update. │\r\n │ │\r\n │ Follow @pnpmjs for updates: https://twitter.com/pnpmjs │\r\n │ │\r\n ╰─────────────────────────────────────────────────────────────────╯\r\n\r\nPackages are cloned from the content-addressable store to the virtual store.\r\n Content-addressable store is at: /workspace/.pnpm-store/v3\r\n Virtual store is at: node_modules/.pnpm\r\nDownloading registry.npmjs.org/typescript/4.9.5: 11.6 MB/11.6 MB, done\r\nProgress: resolved 1137, reused 0, downloaded 1135, added 1137, done\r\nnode_modules/.pnpm/core-js-pure@3.25.5/node_modules/core-js-pure: Running postinstall script, done in 69ms\r\nnode_modules/.pnpm/core-js@3.25.5/node_modules/core-js: Running postinstall script, done in 102ms\r\nnode_modules/.pnpm/esbuild@0.16.17/node_modules/esbuild: Running postinstall script, done in 137ms\r\n\r\ndependencies:\r\n+ @docusaurus/core 2.4.0\r\n+ @docusaurus/preset-classic 2.4.0\r\n+ @easyops-cn/docusaurus-search-local 0.35.0\r\n+ @mdx-js/react 1.6.22\r\n+ @svgr/webpack 6.5.1\r\n+ clsx 1.2.1\r\n+ esbuild-loader 2.21.0\r\n+ file-loader 6.2.0\r\n+ prism-react-renderer 1.3.5\r\n+ react 17.0.2\r\n+ react-dom 17.0.2\r\n+ redocusaurus 1.6.2\r\n+ url-loader 4.1.1\r\n\r\ndevDependencies:\r\n+ @docusaurus/module-type-aliases 2.4.0\r\n+ @tsconfig/docusaurus 1.0.7\r\n+ @types/react 18.0.32\r\n+ @types/react-helmet 6.1.6\r\n+ @types/react-router-dom 5.3.3\r\n+ typescript 4.9.5\r\n\r\nThe integrity of 3271 files was checked. This might have caused installation to take longer.\r\nDone in 59.5s\r\n\r\n> woodpecker@0.0.0 build:woodpecker-plugins /workspace/woodpecker/docs\r\n> cd plugins/woodpecker-plugins && pnpm i && pnpm build\r\n\r\nScope: all 2 workspace projects\r\nDone in 1.7s\r\n\r\n> @woodpecker-ci/plugin-index@0.1.0 build /workspace/woodpecker/docs/plugins/woodpecker-plugins\r\n> pnpm run style && tsc && tsc -p tsconfig.jsx.json\r\n\r\n\r\n> @woodpecker-ci/plugin-index@0.1.0 style /workspace/woodpecker/docs/plugins/woodpecker-plugins\r\n> mkdir -p dist/theme/ && cp src/theme/style.css dist/theme/style.css\r\n\r\n\r\n> woodpecker@0.0.0 start /workspace/woodpecker/docs\r\n> cd ../ && make docs && cd docs && docusaurus start \"--port\" \"4000\"\r\n\r\ngo generate cmd/cli/app.go\r\n# github.com/woodpecker-ci/woodpecker/server/model\r\n../../server/model/secret.go:128:18: undefined: errors.Join\r\nnote: module requires Go 1.20\r\n# github.com/woodpecker-ci/woodpecker/shared/utils\r\n../../shared/utils/context.go:28:25: undefined: context.WithCancelCause\r\nnote: module requires Go 1.20\r\n# github.com/woodpecker-ci/woodpecker/pipeline/frontend/yaml/constraint\r\n../../pipeline/frontend/yaml/constraint/constraint.go:245:68: undefined: errors.Join\r\nnote: module requires Go 1.20\r\ncmd/cli/app.go:40: running \"go\": exit status 2\r\nmake: *** [Makefile:266: docs] Error 1\r\n ELIFECYCLE Command failed with exit code 2.\r\ngitpod /workspace/woodpecker/docs (master) $ \r\n```\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).",[2926,2927,2930],{"name":2866,"color":2867},{"name":2928,"color":2929},"feedback","4B7070",{"name":2931,"color":2932},"devx","47B0E3",1899,"closed","Gitpod not working","2024-02-11T22:59:21Z","https://github.com/woodpecker-ci/woodpecker/issues/1899",0.7510555,{"description":2940,"labels":2941,"number":2946,"owner":2869,"repository":2870,"state":2934,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Component\n\ncli\n\n### Describe the bug\n\nSince updating to 2.4.x woodpecker-cli runs into a runtime error:\r\n\r\n```\r\npanic: runtime error: invalid memory address or nil pointer dereference\r\n[signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x1004c71a8]\r\n\r\ngoroutine 1 [running]:\r\ngo.woodpecker-ci.org/woodpecker/v2/cli/internal/config.Load(0x14000591580)\r\n go.woodpecker-ci.org/woodpecker/v2/cli/internal/config/config.go:53 +0x268\r\ngo.woodpecker-ci.org/woodpecker/v2/cli/common.Before(0x14000591580)\r\n go.woodpecker-ci.org/woodpecker/v2/cli/common/hooks.go:53 +0x70\r\ngithub.com/urfave/cli/v2.(*Command).Run(0x14000597760, 0x14000591580, {0x1400014c000, 0xc, 0xc})\r\n github.com/urfave/cli/v2@v2.27.1/command.go:219 +0x3d0\r\ngithub.com/urfave/cli/v2.(*App).RunContext(0x140001d6e00, {0x101e2cca0, 0x102d70660}, {0x1400014c000, 0xc, 0xc})\r\n github.com/urfave/cli/v2@v2.27.1/app.go:337 +0x514\r\ngithub.com/urfave/cli/v2.(*App).Run(...)\r\n github.com/urfave/cli/v2@v2.27.1/app.go:311\r\nmain.main()\r\n go.woodpecker-ci.org/woodpecker/v2/cmd/cli/main.go:26 +0x48\r\n```\r\n\r\nHere is an example. I export the variables first\r\n\r\n```\r\nexport WOODPECKER_PROJECT=\"test/project\"\r\nexport WOODPECKER_SERVER=\"https://our.server\"\r\nexport WOODPECKER_TOKEN=\"asdf\"\r\n```\r\n\r\nThen i run any command, like `woodpecker-cli pipeline ls` and the error occurs.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\r\n\r\n➜ ~ woodpecker-cli --version\r\nwoodpecker-cli version 2.4.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/faq#which-version-of-woodpecker-should-i-use]",[2942,2943],{"name":2866,"color":2867},{"name":2944,"color":2945},"cli","1d76db",3553,"woodpecker-cli - runtime error: invalid memory address or nil pointer dereference with 2.4.x","2024-04-15T19:18:03Z","https://github.com/woodpecker-ci/woodpecker/issues/3553",0.7526845,{"description":2952,"labels":2953,"number":2956,"owner":2869,"repository":2870,"state":2934,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### 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.",[2954,2955],{"name":2881,"color":2882},{"name":2906,"color":2907},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.75534946,{"description":2962,"labels":2963,"number":2971,"owner":2869,"repository":2870,"state":2934,"title":2972,"updated_at":2973,"url":2974,"score":2975},"like the agent:\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/docker/Dockerfile.agent.multiarch#L21\r\n\r\nref https://docs.docker.com/engine/reference/builder/#healthcheck\r\n\r\nTODO:\r\n- [ ] add subcommand to server that can test against https://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/server/router/router.go#L69\r\n- [ ] use subcommand in container",[2964,2967,2968],{"name":2965,"color":2966},"server","5D7A92",{"name":2906,"color":2907},{"name":2969,"color":2970},"good first issue","76ea72",1943,"Add an healthcheck to server container","2023-07-25T13:55:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1943",0.75747347,{"description":2977,"labels":2978,"number":2981,"owner":2869,"repository":2870,"state":2934,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Component\n\ncli\n\n### Describe the bug\n\n2.7.0 version complains like if it's 2.6.0 and wants to be updated\r\nsee screenshot\r\n\r\n\u003Cimg width=\"1014\" alt=\"Screenshot 2024-07-19 at 22 27 41\" src=\"https://github.com/user-attachments/assets/2e51c78c-9cae-450e-b7a5-4fdcc00707d5\">\r\n\n\n### Steps to reproduce\n\nIn empty dir just do this:\r\n\r\n```bash\r\ncd $(mktemp -d)\r\ncat \u003C\u003CEOF >test.yaml\r\nwhen:\r\n - event: push\r\n branch: test\r\n\r\nsteps:\r\n deploy:\r\n image: bash\r\n commands:\r\n - test\r\nEOF\r\nwoodpecker-cli lint test.yaml\r\n```\r\n\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nit's not a server issue\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]",[2979,2980],{"name":2866,"color":2867},{"name":2944,"color":2945},3941,"woodpecker-cli: 2.7.0 version complains like if it's 2.6.0 and wants to be updated","2024-07-20T13:23:49Z","https://github.com/woodpecker-ci/woodpecker/issues/3941",0.7662893,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8zrGg1okArJeX-LX2TsWE7Dyi6V77c1ul2pbSlXBAEg":-1},"/woodpecker-ci/woodpecker/2858"]