True. We were using it from the fork all along to make sure Hedgehog’s recursive deploy runs. That said, the latest TDS (5.1) does not yet expose a customization point to tap into the post deploy step with something like configuration commit. And .update package metadata only supports a single post-deploy action. I actually scripted unpacking the .update to inject my own class wrapped around Hedgehog’s to do my thing and their thing together but it’s too much mockery and not very future-proof. Dropped that idea in favor of a simple controller endpoint that I can curl into right after deploy. I heard the Hedgehog guys say a few times that 5.2 would enable customizing the post deploy action. Can’t wait! Though I know they are busy getting ready for VS 2015.