I like this approach but I'm not entirely sold on it. In her example, the `category-validations` is branched off from `category-db` and there will be two separa

I like this approach but I'm not entirely sold on it. In her example, the `category-validations` is branched off from `category-db` and there will be two separate PRs. If you start receiving reviews for `category-db` PR and you make those changes then you'll have to rebase it onto the `category-validations` and resolve any conflicts. This will be many times harder if a different developer works on `category-validations` branch. That being said, I can't think of any elegant ways to solve this.