Skip to content

AmbitionEng/django-pgtrigger

View on GitHub ↗Related repositories →

Write Postgres triggers for your Django models

active 2025-03-092026-03-20 (UTC)

Partial coverage11,494 / 12,492 hourly files (92%) · 2 absent upstream · 994 failed, retryable2025-03-082026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
79
Pushes
16
Pull requests
6
Issues
7
Stars
23
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 377 days from 2025-03-09 to 2026-03-20. Pushes: 16 total, peak 5 in a day. Pull requests: 6 total, peak 2 in a day. Issues: 7 total, peak 1 in a day. Comments: 14 total, peak 4 in a day. Stars: 23 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
wesleykendall3516610
esauser3002
pySilver2001
adamchainz1001
shangxiao1000
iamsauravsharma1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#222wesleykendall2026-02-04 13:19
    Running migrations not possible on custom schema
  • Issue comment#220pySilver2025-12-15 11:38
    Support for asynchronous calls
  • Issue#220pySilver2025-12-15 11:25
    Support for asynchronous calls
  • Issue comment#217wesleykendall2025-12-04 22:36
    Add is_ignored
  • Issue comment#217wesleykendall2025-12-04 14:51
    Add is_ignored
  • Issue comment#218wesleykendall2025-12-03 12:09
    Support optimizing the migration operations
  • Releasewesleykendall2025-11-30 23:26
    4.16.0
  • Issue comment#214adamchainz2025-08-19 07:17
    Fix use of core django management command options when using pgtrigger command
  • Releasewesleykendall2025-08-17 02:07
    4.15.4
  • Issue#213wesleykendall2025-08-17 02:06
    pgtrigger management command doesn't play nicely with base options
  • Pull request#214wesleykendall2025-08-17 02:06
  • Issue comment#213wesleykendall2025-08-17 01:25
    pgtrigger management command doesn't play nicely with base options
  • Issue#213shangxiao2025-07-10 07:41
    pgtrigger management command doesn't play nicely with base options
  • Releasewesleykendall2025-06-12 12:00
    4.15.3
  • Pull request#212wesleykendall2025-06-12 11:59
  • Pull request#212wesleykendall2025-06-12 11:57
  • Issue comment#211wesleykendall2025-06-10 17:38
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue comment#211esauser2025-06-10 17:09
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue comment#211wesleykendall2025-06-10 16:25
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue comment#211wesleykendall2025-06-10 12:58
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue#211wesleykendall2025-06-10 12:58
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue comment#211esauser2025-06-09 14:34
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue comment#211wesleykendall2025-06-09 14:26
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue#211esauser2025-06-05 20:52
    PostgreSQL 16 Compatibility Issue: Geometry Field Triggers Fail Due to Overloaded Operator Resolution
  • Issue comment#205wesleykendall2025-04-26 02:17
    Attempting to run makemigrations with Django 5.0, 5.1 and condition AnyChange results in error

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 23 stars here means stars gained during the window, not the repo's star count.