Comment 1 for bug 1931256

This is true, though we strongly recommend that you instead push to a repository owned by you even if you have permission to push directly to the target (so `/~seb128/<project>` rather than just `/<project>`). There's usually no reason not to do that and it's much clearer what's going on.

At present we don't have independent subscriptions for merge proposals, nor for individual git branches. Unless we add one of those, the only way to fix this would involve subscribing you to the entire repository, which I suspect would be too heavyweight.