I have a project for which the main branch in bitbucket server is set to develop.
Many of my plugins have a specific behavior when the current branch is the main branch, and during my tests on other project which have a master main branch, everything was working well.

But even if the main branch is set to develop, the DRONE_REPO_BRANCH is set to master.
Is it a bitbucket related bug like the [CI SKIP] one? Or is there something else?



This is happening with me but with Gitea. The default branch set in Gitea for my repos is “main”, but the docker plugin skips image build and push when the commit was to branch “main” but was not tagged. Gitea sends a “default_branch” key in the webhooks, perhaps the value here should be used as the name of the default branch? (code here)