Skip to content

๐Ÿ› ๏ธ Simplifies EF management by helping to squash migrations

active 2024-11-11 โ†’ 2026-04-07 (UTC)

Complete coverage26,550 / 26,550 hourly files (100%) ยท 2 absent upstream2023-08-15 โ†’ 2026-08-25 (UTC)
Events
75
Pushes
13
Pull requests
3
Issues
4
Stars
25
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 513 days from 2024-11-11 to 2026-04-07. Pushes: 13 total, peak 3 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 4 total, peak 1 in a day. Comments: 17 total, peak 8 in a day. Stars: 25 total, peak 3 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
pdevito32713110
jasekiw6005
dkattan2010
cremor1001
gust421010
Nick-Case1001

Recent activity

Latest issues, pull requests and releases

  • Issue#7pdevito32026-04-07 03:06
    Please add a LICENSE file
  • Issue comment#1jasekiw2025-12-29 17:17
    Issues with target model producing error: "X could not be found in target model"
  • Issue#3pdevito32025-11-10 03:30
    -d option is invalid, path appears to be positional. -t and -y options missing from published version
  • Issue comment#3pdevito32025-11-10 03:30
    -d option is invalid, path appears to be positional. -t and -y options missing from published version
  • Releasepdevito32025-11-10 03:29
    v0.2.0
  • Issue comment#3Nick-Case2025-11-06 11:37
    -d option is invalid, path appears to be positional. -t and -y options missing from published version
  • Issue comment#5pdevito32025-09-02 18:39
    Enclose migrations in their own scopes
  • Issue comment#3pdevito32025-04-03 12:44
    -d option is invalid, path appears to be positional. -t and -y options missing from published version
  • Pull request#4dkattan2025-04-03 11:42
  • Issue#3dkattan2025-04-03 11:38
    -d option is invalid, path appears to be positional. -t and -y options missing from published version
  • Pull request#2pdevito32025-01-23 14:23
  • Pull request#2gust422025-01-23 10:30
  • Issue comment#1pdevito32024-11-14 14:56
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1jasekiw2024-11-14 14:52
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1pdevito32024-11-14 13:35
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1cremor2024-11-14 07:44
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1pdevito32024-11-13 22:23
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1pdevito32024-11-13 19:19
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1jasekiw2024-11-13 19:16
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1jasekiw2024-11-13 18:31
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1pdevito32024-11-13 18:00
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1jasekiw2024-11-13 16:37
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1pdevito32024-11-13 16:37
    Issues with target model producing error: "X could not be found in target model"
  • Issue comment#1pdevito32024-11-13 16:33
    Issues with target model producing error: "X could not be found in target model"
  • Issue#1jasekiw2024-11-13 15:58
    Issues with target model producing error: "X could not be found in target model"

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