[PATCH v4 0/4] Store the 'actor' responsible for events
dja at axtens.net
Wed Dec 4 17:20:55 AEDT 2019
> Thanks for the quick turnaround on this. I squashed patches 3 and 4,
> added a release note, fixed a minor issue with the schema documentation
> and pushed everything. It will form part of Patchwork v2.2 which I'm
> hoping to get out this coming week.
Record-breaking turnarounds all around - thanks for applying this Stephen.
>> Changes since v3:
>> - Drop wiring up the actor in patch-created, patch-completed, and
>> series-completed events (as there are triggered by emails).
>> - Add patch #4 to allow filtering events by actor.
>> Have fun!
>> Johan Herland (4):
>> models.Event: Add the user responsible for the event
>> Include the responsible actor in applicable events
>> /api/events: Add 'actor' field to generated JSON
>> /api/events: Allow filtering by 'actor' field
>> docs/api/schemas/latest/patchwork.yaml | 6 ++++
>> docs/api/schemas/patchwork.j2 | 8 +++++
>> docs/api/schemas/v1.2/patchwork.yaml | 6 ++++
>> docs/usage/overview.rst | 3 ++
>> patchwork/api/event.py | 10 ++++--
>> patchwork/api/filters.py | 5 ++-
>> patchwork/migrations/0037_event_actor.py | 21 +++++++++++
>> patchwork/models.py | 10 +++++-
>> patchwork/signals.py | 3 ++
>> patchwork/tests/api/test_event.py | 46 ++++++++++++++++++++++++
>> patchwork/tests/test_events.py | 7 ++++
>> 11 files changed, 120 insertions(+), 5 deletions(-)
>> create mode 100644 patchwork/migrations/0037_event_actor.py
> Patchwork mailing list
> Patchwork at lists.ozlabs.org
More information about the Patchwork