zulip/zerver/webhooks/clubhouse
Eeshan Garg cfe0f6b56d webhooks/clubhouse: Account for bug in GitHub branch payloads.
This change was prompted by a possible bug on Clubhouse's end. In
general, if a branch is added, it also prompts a workflow state
transition in its primary story.

However, our webhook error logs show an erroneous payload where
the same branch is added to another story, but there is no
workflow state transition. Also, both the stories are grouped in
the same payload, which confused/broke our code. Ideally, this
shouldn't happen and is most likely a bug on Clubhouse's end.
In most cases, changes included in Clubhouse payloads never
pertain to more than one parent entity (stories) simultaneously,
and we usually operate under the assumption that the changes
included therein are related to each other in terms of their
parent object (story or epic) and not a child object (the GitHub
branch).
2019-02-20 16:32:42 -08:00
..
fixtures webhooks/clubhouse: Support epic_archive events. 2019-02-20 16:32:42 -08:00
__init__.py
doc.md
tests.py webhooks/clubhouse: Support epic_archive events. 2019-02-20 16:32:42 -08:00
view.py webhooks/clubhouse: Account for bug in GitHub branch payloads. 2019-02-20 16:32:42 -08:00