We are using tags to trigger our build workflows. For our production builds, we are using the
main branch, whilst our default branch for development and other builds is named
dev. E.g., to kick off a production build, we apply a tag to the
main branch and push it to our repo on Github.
We recently noticed that the $BITRISE_GIT_BRANCH environment variable is still set to
dev, even when our tags that trigger a build are on the
main branch and are building off from the
main branch. Is this expected behavior? Does the environment variable get set by the trigger?
It doesn’t seem to cause any problems, but when we added the default Slack message step to our workflow, it contains $BITRISE_GIT_BRANCH in it, and it was a little disconcerting to see what appears to be the wrong branch in the notification.