Skip to content

IntegreSQL manages isolated PostgreSQL databases for your integration tests.

active 2023-08-162026-05-27 (UTC)

Complete coverage26,646 / 26,646 hourly files (100%) · 2 absent upstream2023-08-152026-08-29 (UTC)
Events
260
Pushes
10
Pull requests
4
Issues
11
Stars
213
Forks
8

Activity over time

Daily event counts in the loaded window

Line chart, 1016 days from 2023-08-16 to 2026-05-27. Pushes: 10 total, peak 6 in a day. Pull requests: 4 total, peak 3 in a day. Issues: 11 total, peak 5 in a day. Comments: 10 total, peak 5 in a day. Stars: 213 total, peak 16 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
majodev251036
bartoszhernas2001
Rudomitori2000
luisgc931000
Shaddix1001
schuerg1000
saratscheff1010
christophsturm1001
vasilzhigilei1001

Recent activity

Latest issues, pull requests and releases

  • Issue#23majodev2025-12-23 12:54
    Use STRATEGY=FILE_COPY for Postgres>=v15
  • Issue comment#17vasilzhigilei2025-05-30 15:35
    New version change of behaviour, Integresql is not waiting for DB to finish creating
  • Issue#21Rudomitori2025-01-19 11:50
    Intrgresql returns non-existent database when long hash is used
  • Issue#20Rudomitori2025-01-19 08:20
    Non-URL-safe symbols in hashes
  • Pull request#19saratscheff2024-11-15 18:35
  • Issue comment#17christophsturm2024-07-17 14:17
    New version change of behaviour, Integresql is not waiting for DB to finish creating
  • Issue#18luisgc932024-05-20 20:30
    Mermaid diagrams appear broken in readme
  • Issue comment#17Shaddix2024-03-05 15:05
    New version change of behaviour, Integresql is not waiting for DB to finish creating
  • Issue#17bartoszhernas2024-02-09 12:49
    New version change of behaviour, Integresql is not waiting for DB to finish creating
  • Issue comment#4majodev2024-02-01 09:44
    Automatic cleanup of no longer used templates DBs
  • Issue comment#2majodev2024-01-30 18:53
    ReturnTestDatabase does not wipe database before returning to pool
  • Issue#2majodev2024-01-30 18:53
    ReturnTestDatabase does not wipe database before returning to pool
  • Issue comment#5majodev2024-01-30 18:53
    Help setting up IntegreSQL
  • Issue#5majodev2024-01-30 18:53
    Help setting up IntegreSQL
  • Issue comment#7majodev2024-01-30 18:53
    404 for readme "install locally" URL
  • Issue#7majodev2024-01-30 18:53
    404 for readme "install locally" URL
  • Issue comment#13majodev2024-01-30 18:52
    The database returned by `GetTestDatabase` is dirty if a test has already been run.
  • Issue#13majodev2024-01-30 18:52
    The database returned by `GetTestDatabase` is dirty if a test has already been run.
  • Issue comment#15majodev2024-01-30 18:52
    Support arm64 CPU architecture for Apple Silicon (M1) compatibility
  • Issue#15majodev2024-01-30 18:52
    Support arm64 CPU architecture for Apple Silicon (M1) compatibility
  • Releasemajodev2024-01-30 18:51
    v1.1.0
  • Pull request#14majodev2024-01-30 18:48
  • Pull request#16majodev2024-01-30 18:48
  • Pull request#16majodev2024-01-30 18:46
  • Issue comment#15bartoszhernas2023-09-25 14:05
    Support arm64 CPU architecture for Apple Silicon (M1) compatibility

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