I&#x27;ve done this previously, and it works, but it creates a very messy history where you have merges going back and forth. We typically had several merges to get changes in from master for each feature branch, even if they only lasted for a few days (inside a sprint). Then there&#x27;s the final merge back to master. If you look at the repo from afar after a couple of features and weeks, it gets very hard to read.