\n\nThis is inconsistent with how secrets are handled elsewhere in Woodpecker:\n\nIn the Secrets section, users cannot view secret values (they can only update them).\n\nIn the Forge edit form, the OAuth Client Secret is already hidden by default.\n\n### Suggested solution\n\nIt would be preferable if the Git password field in the Forge UI were also hidden (like secrets), so that even Woodpecker admins cannot view these values in plaintext once they are saved.\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/versions]\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.",[3139],{"name":3140,"color":3141},"feature","180DBE",5471,"woodpecker-ci","woodpecker","open","Hide Bitbucket Data Center credentials in Forge UI","2025-08-31T10:17:07Z","https://github.com/woodpecker-ci/woodpecker/issues/5471",0.74935,{"description":3151,"labels":3152,"number":3156,"owner":3143,"repository":3144,"state":3145,"title":3157,"updated_at":3158,"url":3159,"score":3160},"### Component\n\nserver\n\n### Describe the bug\n\nSee https://codeberg.org/Codeberg-CI/feedback/issues/120\r\n\r\nC/p issue description:\r\n\r\n1. Create repo in Gitea\r\n2. Enable it in WP\r\n3. Delete repo in Gitea\r\n4. Create repo with the same name in Gitea\r\n5. Try to enable it again\r\n\r\n-> error\r\n\r\nWhen enabling a repo, there should be a check for an existing one in the DB and if one exists, it should be deleted. \n\n### System Info\n\n```shell\n`next-dfc2c265b1` (Dec 20th)\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/main/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).",[3153],{"name":3154,"color":3155},"bug","d73a4a",3020,"Re-enabling a WP repo after previous deletion/recreation in forge leads to DB deadlock","2025-01-23T11:41:11Z","https://github.com/woodpecker-ci/woodpecker/issues/3020",0.76709723,{"description":3162,"labels":3163,"number":3167,"owner":3143,"repository":3144,"state":3145,"title":3168,"updated_at":3169,"url":3170,"score":3171},"### Component\n\nserver\n\n### Describe the bug\n\nWhen you are not a Woodpecker admin https://ci.woodpecker-ci.org/orgs/2 gives an error.\r\nThe UI shows it as `An unknown error occurred` in a flash message with a red background.\r\nThe network fan shows a call to https://ci.woodpecker-ci.org/api/orgs/2 returning 401 Unauthorized\r\n\r\nAs an admin it returns \r\n```\r\n{\"id\":2,\"name\":\"woodpecker\",\"is_user\":true}\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-a28e2e1920\"}\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/main/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).",[3164],{"name":3165,"color":3166},"enhancement","7E1FE4",2983,"Allow to view (public) repos from other orgs (if not an admin)/users","2024-01-02T09:31:58Z","https://github.com/woodpecker-ci/woodpecker/issues/2983",0.7838895,{"description":3173,"labels":3174,"number":3179,"owner":3143,"repository":3144,"state":3145,"title":3180,"updated_at":3181,"url":3182,"score":3183},"As the current migration of #4762 will only fix user org names, I am thinking of a global repair api endpoint that could do some additional tasks like:\r\n- updating user names from forge\r\n- org names from forge\r\n- checking each user has an user org\r\n- updating user permissions\r\n- doing repo repairs\r\n ",[3175,3178],{"name":3176,"color":3177},"server","5D7A92",{"name":3140,"color":3141},4807,"Admin \"repair\" mode","2025-02-13T10:50:43Z","https://github.com/woodpecker-ci/woodpecker/issues/4807",0.7867521,{"description":3185,"labels":3186,"number":3188,"owner":3143,"repository":3144,"state":3145,"title":3189,"updated_at":3190,"url":3191,"score":3192},"### Component\n\nserver\n\n### Describe the bug\n\nWe changed the Bitbucket build status key to use the same common method as other forges when reporting back the build status to the forge. It works as expected for Woodpecker instances that have not been running for a long time, but it starts failing on those that already have a lot of workflow runs.\n\nThe problem is the template we use to generate the key: \n\nhttps://github.com/woodpecker-ci/woodpecker/blob/1f23da379ef4ca103138c066baafcd65260b4005/cmd/server/flags.go#L279\n\nTemplate: \"{{ .context }}/{{ .event }}/{{ .workflow }}{{if not (eq .axis_id 0)}}/{{.axis_id}}{{end}}\"\n\nBitbucket has a maximum key length of 40 characters. It works as expected if axis_id is not added. The generated key without the axis_id has ~30 characters:\n- ci/woodpecker/branch/woodpecker (31)\n- ci/woodpecker/pr/woodpecker (27)\n\nBefore proposing a fix, I want to understand the purpose of the axis_id. I could not figure it out. What is the axis_id used for?\n\n### Steps to reproduce\n\n1. Woodpecker instance with axis_id > 100000000\n2. Trigger a Woodpecker workflow\n\n### Expected behavior\n\n1. The key should always be less than 40 characters for the Bitbucket forge\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-aac914cfae\"}\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]",[3187],{"name":3154,"color":3155},5176,"BitBucket build status key is too long","2025-05-14T07:35:49Z","https://github.com/woodpecker-ci/woodpecker/issues/5176",0.79596394,{"description":3194,"labels":3195,"number":3200,"owner":3143,"repository":3144,"state":3201,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### Component\n\nserver\n\n### Describe the bug\n\nWhen build finishes(either successfully or with failure) the status doesn't get updated, even though the commit status of the last commit on the PR is updated just fine.\n\nI was able to trace back this bug to this PR: https://github.com/woodpecker-ci/woodpecker/pull/4724\n\nNow I see the need for the `Ref` to be set when updating the build status but it turns out that `pipeline.Ref` doesn't have a correct value. In my case it would set only the ref as follows: `refs/pull-requests/\u003CpullRequestID>/from`. I was able to find that `Ref` gets set [here](https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L122) and I believe this is wrong, it's not a \"valid\" git ref and if ref is set to an invalid value BitBucket will not set the build status for that PR(https://community.atlassian.com/forums/Bitbucket-questions/Re-Builds-not-appearing-in-pull-requests/qaq-p/1805991/comment-id/65864#M65864).\n\nI suggest that we change the code from above to:\n```go\nRef: fmt.Sprintf(\"refs/heads/%s\", ev.PullRequest.Source.DisplayID),\n```\nI believe this would fix the issue, and I would like to work on it if possible.\n\nAdding: @Levy-Tal as he worked on PR mentioned above and @langecode because he is the main contributor behind the BitBucket Datacenter forge integration.\n\n\n### Steps to reproduce\n\n1. Open a PR with woodpecker pipelines on BitBucket Datacenter\n2. Trigger a build on the last commit of that PR\n3. Wait for the build to finish\n4. Observe that there is no status on the PR itself\n\n### Expected behavior\n\nThere should be a build status on the PR.\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nHelm chart version: 3.1.0\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]",[3196,3197],{"name":3154,"color":3155},{"name":3198,"color":3199},"forge/bitbucket","E96280",5158,"closed","PR build status does not get updated on BitBucket Datacenter","2025-05-13T15:29:01Z","https://github.com/woodpecker-ci/woodpecker/issues/5158",0.7673759,{"description":3207,"labels":3208,"number":3210,"owner":3143,"repository":3144,"state":3201,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a pipeline with multiple workflows starts a correct status is sent at first BitBucket correctly displays that build is in progress. When the build finishes however, only one build is displayed as finished but the other one is still in progress marking the whole commit as in progress(this is internal BitBucket logic). \n\nHere is a pipeline that has two workflows:\n\n\n\nAnd here is the outcome on BitBucket:\n\n\n\nI asked @langecode if he can take a look and we realized that there is a problem in BitBucket forge implementation of `Status` function. It looks like that for each call of `Status` function we send a status of the whole pipeline when we should've sent a status of individual workflows. I.e. change status of https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L314\n\nTo:\n```go\nState: convertStatus(workflow.State)\n```\n\n### Steps to reproduce\n\n1. Run woodpecker with BitBucket Datacenter forge\n2. Create a pipeline that has multiple workflows\n3. Let the pipeline finish on woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nBitBucket Datacenter version: v8.18.1\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]",[3209],{"name":3154,"color":3155},5177,"Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.76788485,{"description":3216,"labels":3217,"number":3220,"owner":3143,"repository":3144,"state":3201,"title":3221,"updated_at":3222,"url":3223,"score":3224},"Hey there, we're trying to downgrade from drone.io to woodpecker.\r\nSo far everything is up and running, but when I try to authorize vi bitbucket server I'd just show Access approved message and never redirects back to woodpecker.\r\nIt does work fine with drone though.\r\nThanks",[3218,3219],{"name":3154,"color":3155},{"name":3198,"color":3199},188,"BitBucket auth is not working","2023-07-31T17:56:39Z","https://github.com/woodpecker-ci/woodpecker/issues/188",0.7712572,{"description":3226,"labels":3227,"number":3232,"owner":3143,"repository":3144,"state":3201,"title":3233,"updated_at":3234,"url":3235,"score":3236},"When creating / editing a bitbucket forge in the UI we can currently change the host and set advanced options although they have no effect for the forge config.",[3228,3231],{"name":3229,"color":3230},"ui","46DEA2",{"name":3165,"color":3166},5441,"Hide forge options that can't be changed in UI","2025-08-27T06:21:52Z","https://github.com/woodpecker-ci/woodpecker/issues/5441",0.77748823,{"description":3238,"labels":3239,"number":3243,"owner":3143,"repository":3144,"state":3201,"title":3244,"updated_at":3245,"url":3246,"score":3247},"# Required open issues / PRs\r\n- [x] #4314 fixed\r\n- [x] v2.8.0 with https://github.com/woodpecker-ci/woodpecker/issues/4306 released\r\n- [x] service settings (https://github.com/woodpecker-ci/woodpecker/pull/4336)\r\n- [ ] ...\r\n\r\n# Breaking changes (sorted by impact for users)\r\n\r\n- change of webhook => requires repair all #4013 \r\n- removed deprecated keywords: \r\n - `pipeline`, `platform`, `branches`, `steps.[name].secrets` #4363 #3916 \r\n - `steps.[name].group`, removed `include` / `exclude` from when filter #4016\r\n- removed privileged plugins: `plugins/docker`, `plugins/gcr`, `plugins/ecr`, `woodpeckerci/plugin-docker-buildx` #3846\r\n- removed alternative names for secrets, use `environment` with `from_secret` #4016\r\n- removed `environment` for `when.evaluate` #4016\r\n- removed slice definition for env vars #4016\r\n- #4005\r\n- #3785\r\n- stopped secrets from being uppercased #4053\r\n- replaced cli `registry` command with `repo registry` #4017\r\n- some changes / removals of api routes / json properties #3968\r\n- cron not using seconds anymore #3785\r\n- (Left out less relevant changes, Please add other impact-full changes)\r\n\r\n# Tasks before releasing\r\n- Update go imports to `\"go.woodpecker-ci.org/woodpecker/v3/...\"`\r\n- Check and adjust migration docs, so users can simply follow and get to the new version. testing\r\n- Create new docs version 3.0\r\n- Create blog post\r\n- Test version \r\n- Post on social media",[3240],{"name":3241,"color":3242},"governance","A46EFE",4320,"Release plan for v3.0.0","2025-01-18T23:31:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4320",0.77875304,["Reactive",3249],{},["Set"],["ShallowReactive",3252],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fm39LxgjMWJ2P3KbKusyFW4-eCjKWbMCjL7tX5V-kP58":-1},"/woodpecker-ci/woodpecker/1138"]