\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]",[2898,2899],{"name":2868,"color":2869},{"name":2900,"color":2901},"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.7397675,{"description":2908,"labels":2909,"number":2915,"owner":2874,"repository":2875,"state":2876,"title":2916,"updated_at":2917,"url":2918,"score":2919},"We could have a workspace preparation docker image that would be run as root and do necessary tasks to prepare everything so that the skip clone would work and also clone steps could be run as non-root images?\n\nMaybe even a woodpecker server could act as docker registry to serve container image for this so that it would work in instances that have no internet connection\n\n_Originally posted by @lafriks in https://github.com/woodpecker-ci/woodpecker/pull/5056#issuecomment-2784618118_",[2910,2911,2913],{"name":2871,"color":2872},{"name":2912,"color":2889},"backend/docker",{"name":2914,"color":2889},"backend/kubernetes",5082,"Add workspace preparation hidden step before clone steps","2025-04-07T21:24:54Z","https://github.com/woodpecker-ci/woodpecker/issues/5082",0.76536196,{"description":2921,"labels":2922,"number":2927,"owner":2874,"repository":2875,"state":2928,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### 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.",[2923,2924],{"name":2900,"color":2901},{"name":2925,"color":2926},"feature","180DBE",1489,"closed","Beautify display of commit messages with bodies and/or footers","2023-08-20T16:52:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1489",0.67848897,{"description":2934,"labels":2935,"number":2937,"owner":2874,"repository":2875,"state":2928,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Component\n\nserver\n\n### Describe the bug\n\nThere is unnecessary empty table `registry_v031` in database.\n\n### Steps to reproduce\n\n```sql\r\npostgres=# \\c woodpecker\r\nYou are now connected to database \"woodpecker\" as user \"postgres\".\r\nwoodpecker=# \\dt\r\n List of relations\r\n Schema | Name | Type | Owner\r\n--------+------------------+-------+------------\r\n public | agents | table | woodpecker\r\n public | configs | table | woodpecker\r\n public | crons | table | woodpecker\r\n public | files | table | woodpecker\r\n public | forges | table | woodpecker\r\n public | log_entries | table | woodpecker\r\n public | migration | table | woodpecker\r\n public | orgs | table | woodpecker\r\n public | perms | table | woodpecker\r\n public | pipeline_configs | table | woodpecker\r\n public | pipelines | table | woodpecker\r\n public | redirections | table | woodpecker\r\n public | registries | table | woodpecker\r\n public | registry_v031 | table | woodpecker\r\n public | repos | table | woodpecker\r\n public | secrets | table | woodpecker\r\n public | server_configs | table | woodpecker\r\n public | steps | table | woodpecker\r\n public | tasks | table | woodpecker\r\n public | users | table | woodpecker\r\n public | workflows | table | woodpecker\r\n(21 rows)\r\n\r\nwoodpecker=# select * from registry_v031;\r\n registry_id | registry_repo_id | registry_addr | registry_username | registry_password\r\n-------------+------------------+---------------+-------------------+-------------------\r\n(0 rows)\r\n``` \n\n### Expected behavior\n\nThere is no garbage table.\n\n### System Info\n\n```shell\nWoodpecker `2.7.0`, Postgres 16.\n```\n\n\n### Additional context\n\n#3806\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]",[2936],{"name":2868,"color":2869},4104,"Garbage table registry_v031","2024-09-14T11:41:15Z","https://github.com/woodpecker-ci/woodpecker/issues/4104",0.6907914,{"description":2943,"labels":2944,"number":2948,"owner":2874,"repository":2875,"state":2928,"title":2949,"updated_at":2950,"url":2951,"score":2952},"https://ci.woodpecker-ci.org/repos/3780/pipeline/20983/15\r\n\r\nbuild-deb-rpo errors with:\r\n```\r\nVERSION_NUMBER=0.0.0 nfpm package --config ./nfpm/agent.yaml --target dist --packager deb\r\nmatching \"./woodpecker-agent.service\": file does not exist\r\nmake: *** [Makefile:319: bundle-agent] Error 1\r\n```",[2945],{"name":2946,"color":2947},"build","6AB8BA",4152,"fix 'binary' workflow","2024-10-05T14:43:41Z","https://github.com/woodpecker-ci/woodpecker/issues/4152",0.6981475,{"description":2954,"labels":2955,"number":2958,"owner":2874,"repository":2875,"state":2928,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe spaces in task output should be kept.\r\n\r\n\r\n\n\n### System Info\n\n```shell\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"next-9feb6be9\"\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] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[2956,2957],{"name":2868,"color":2869},{"name":2900,"color":2901},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.71383536,{"description":2964,"labels":2965,"number":2971,"owner":2874,"repository":2875,"state":2928,"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",[2966,2967,2968],{"name":2871,"color":2872},{"name":2925,"color":2926},{"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.7310305,{"description":2977,"labels":2978,"number":2979,"owner":2874,"repository":2875,"state":2928,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Clear and concise description of the problem\n\nPeople miss this feature Drone CI has: https://docs.drone.io/runner/exec/overview/\r\n\r\nIt allows you to execute a build on a systems default shell, without isolation.\n\n### Suggested solution\n\nA user should be able to add and choose agents for a repo.\n\n### Alternative\n\nPeople keep using Drone CI.\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.",[],847,"Support \"Exec runner\"","2022-03-23T16:56:18Z","https://github.com/woodpecker-ci/woodpecker/issues/847",0.7366657,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fon1MR7vPCMltdV_sm0lF2sTqQK9ImCQtc7VMd5twRBo":-1},"/woodpecker-ci/woodpecker/4113"]