Asana integration (Inbox spamming)
Description
There's a problem related to the Asana service, causing spamming of Asana Inbox. Personally, I think it's because of c calculating which commits would be sent to the Asana. For new branches Gitlab usually send all commits between the last revision in the default branch and the last revision of the current branch (GitPushService, line 40).
But lets pretend there's a default branch master and working branch dev and the most of the work happens inside the dev branch. Every time a developer pushes new branch (branched from the dev, not from the master) to the repository, Gitlab would sent every commit between the master and current branch, but not the dev. Which means, there would be duplicating messages about the same commits. And probably there would be really a lot of them... To the point when the it became hard to use Inbox because of spam, because we got more than one dev branch per major feature.
Proposal
This is exactly why I propose to provide new settings to the built-in Gitlab integration with Asana. Something like a checkbox "Turn on uniq notifications". When the box is checked, Gitlab wouldn't send duplicates to the Asana.
Moreover, I would gladly implement this feature myself and make the merge request if this proposal is worthy (and I guess it is, because our team gets spammed with this duplicating notifications).