What does this MR do?
The merge request removes some redundant calls, which led to duplicate events for removed tags.
Are there points in the code the reviewer needs to double check?
I'm not entirely sure my assessment how the event is triggered is correct. This should be verified to ensure that the change doesn't break unrelated functionality.
Why was this MR needed?
Issue #35406 (moved): Two events are created for a delete tag event and also two notifications.
Diagnosis: When a tag is removed, the PostReceive worker is being triggered, which in turn triggers GitTagPushService to process the tag changes. This in turn uses EventCreateService to track a push and fires project hooks and services. Thus the explicit calls in Tags::DestroyService are redundant, leading to duplicate events being tracked.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
Changelog entry added, if necessary
API support added
Added for this feature/bug
All builds are passing
Conform by the merge request performance guides
Conform by the style guides
Branch has no merge conflicts with
master(if it does - rebase it please)
Squashed related commits together