Skip to content

feat: Add Linear action item syncing for incidents #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
spalmurray wants to merge 29 commits into
base: main
Choose a base branch
from

Add Linear config to CI toml so action item tests run

4bc74d3
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Open

feat: Add Linear action item syncing for incidents #139

Add Linear config to CI toml so action item tests run
4bc74d3
Select commit
Loading
Failed to load commit list.
GitHub Actions / warden: django-perf-review completed Apr 14, 2026 in 7m 32s

1 issue

django-perf-review: Found 1 issue (1 high)

High

Write loop: update_or_create called per Linear issue in sync loop - `src/firetower/incidents/services.py:202-215`

The sync_action_items_from_linear function calls ActionItem.objects.update_or_create() inside a loop for each Linear issue (lines 202-215). With N issues, this executes N separate INSERT/UPDATE operations. Additionally, _resolve_assignee (lines 196-200) may trigger additional database calls per issue. While throttling (300s) and per-incident scoping limit impact, incidents with many action items will experience N+1 write latency.

Duration: 451.7s · Tokens: 1.1M in / 13.4k out · Cost: $2.16 (+extraction: $0.00)

Annotations

Check failure on line 215 in src/firetower/incidents/services.py

See this annotation in the file changed.

@github-actions github-actions / warden: django-perf-review

Write loop: update_or_create called per Linear issue in sync loop 

The sync_action_items_from_linear function calls ActionItem.objects.update_or_create() inside a loop for each Linear issue (lines 202-215). With N issues, this executes N separate INSERT/UPDATE operations. Additionally, _resolve_assignee (lines 196-200) may trigger additional database calls per issue. While throttling (300s) and per-incident scoping limit impact, incidents with many action items will experience N+1 write latency.
View more details on GitHub Actions