Skip to content

Assertions for database

active 2024-11-082026-03-22 (UTC)

Partial coverage14,662 / 17,850 hourly files (82%) · 2 absent upstream · 3,187 failed, retryable2024-07-282026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
113
Pushes
8
Pull requests
29
Issues
9
Stars
4
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 500 days from 2024-11-08 to 2026-03-22. Pushes: 8 total, peak 2 in a day. Pull requests: 29 total, peak 4 in a day. Issues: 9 total, peak 1 in a day. Comments: 31 total, peak 5 in a day. Stars: 4 total, peak 1 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
dependabot[bot]3902613
VanRoy19706
jmaniquet6014
scordio5111
sonarcloud[bot]5005
fl0rian-p3001
Copilot2011
bhargavkumar-651000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#329VanRoy2026-02-21 09:33
    [Feature Request] Consider a way for DB assertions to coexist with org.assertj.core.api.Assertions
  • ReleaseVanRoy2026-02-21 09:32
    v3.0.2
  • Issue#332VanRoy2026-02-21 09:18
    Migrate JUnit assertion to AssertJ core
  • Issue comment#332jmaniquet2026-02-15 21:27
    Migrate JUnit assertion to AssertJ core
  • Issue comment#332jmaniquet2026-02-15 19:30
    Migrate JUnit assertion to AssertJ core
  • Issue comment#328fl0rian-p2026-02-14 19:33
    BLOB column always shows up in Changes
  • Issue comment#330jmaniquet2026-02-14 17:24
    Makes Core and DB assertions coexist with only one import
  • Issue comment#330VanRoy2026-02-11 19:35
    Makes Core and DB assertions coexist with only one import
  • Issue comment#330VanRoy2026-02-09 20:48
    Makes Core and DB assertions coexist with only one import
  • Issue comment#330scordio2026-02-07 10:34
    Makes Core and DB assertions coexist with only one import
  • Pull request#330jmaniquet2026-02-07 10:29
  • Issue comment#329jmaniquet2026-02-05 18:16
    [Feature Request] Consider a way for DB assertions to coexist with org.assertj.core.api.Assertions
  • Issue#329VanRoy2026-02-04 20:29
    [Feature Request] Consider a way for DB assertions to coexist with org.assertj.core.api.Assertions
  • Issue#329jmaniquet2026-01-31 12:51
    [Feature Request] Consider a way for DB assertions to coexist with org.assertj.core.api.Assertions
  • Issue comment#328VanRoy2026-01-09 20:56
    BLOB column always shows up in Changes
  • Issue#327VanRoy2026-01-09 20:52
    Incorrect documentation
  • Issue#325VanRoy2025-12-21 18:53
    Table containing an array column always register modification changes between start point and endpoint
  • Issue#324VanRoy2025-12-11 19:58
    Add toString() and equals() implementations for core domain types (Table, Row, Value, Column)
  • Issue comment#324VanRoy2025-12-11 19:58
    Add toString() and equals() implementations for core domain types (Table, Row, Value, Column)
  • Issue comment#321dependabot[bot]2025-09-23 02:01
    Bump org.assertj:assertj-core from 3.21.0 to 3.27.5
  • Pull request#321dependabot[bot]2025-09-23 02:01
  • Issue comment#318dependabot[bot]2025-09-19 02:01
    Bump org.assertj:assertj-core from 3.21.0 to 3.27.4
  • Pull request#318dependabot[bot]2025-09-19 02:01
  • Pull request#320dependabot[bot]2025-09-14 13:37
  • Issue comment#311dependabot[bot]2025-09-14 13:36
    Bump net.bytebuddy:byte-buddy from 1.12.1 to 1.17.0

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