We have an issue where “develop” is set as the default branch in our repo’s settings, but whenever a PR is first created, it’s not actually set as the default branch. Instead, it always initially sets the branch to “master”, even though we can see here in the drop-down that “develop” is labeled as “default”:
Does anyone know why it’s not respecting the default “develop” branch by actually setting new PRs to that branch?
This causes large issues for us because if we don’t notice and approve a PR to master, it triggers a GitHub action which releases everything in “develop” to “master”.