Interesting suggestion. I'd love to know more about what this would unlock for your workflow!
Sure thing. We are constantly working on features in short-lived feature branches that we merge to master. The usual flow is merge from master, work on a feature for 1-7 days, merge to master. We use this flow for almost everything -- enhancements, bug fixes, etc.
We deploy major releases approximately once a once, and always tag the commit that was deployed. When there is occasionally an urgent hotfix, we want to branch off of this tag so that we don't accidentally need to release anything that we've been working on since the release. So it looks like this:
# build a feature
git checkout master
git checkout -b feature/my-awesome-feature # we do this via bitbucket UI
git checkout master && git merge feature/my-awesome-feature # this is really a pull request
git tag -a release-10.2.1
# build more features. Hooray!
# oh no...a major production bug. I want to fix it without involves those new features.
git checkout release-10.2.1
git checkout -b feature/my-urgent-bugfix # this is the step we can't do via bitbucket UI today
git commit -m "this fixes it"
git tag -a release-10.2.2