graphql-ruby plugin for caching parts of the response
active 2023-08-22 → 2026-06-07 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1021 days from 2023-08-22 to 2026-06-07. Pushes: 81 total, peak 15 in a day. Pull requests: 48 total, peak 4 in a day. Issues: 23 total, peak 3 in a day. Comments: 53 total, peak 5 in a day. Stars: 71 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| DmitryTsepelev | 156 | 81 | 35 | 26 |
| mgruner | 10 | 0 | 1 | 6 |
| danielhartnell | 5 | 0 | 0 | 3 |
| noma4i | 4 | 0 | 1 | 3 |
| tsugitta | 4 | 0 | 0 | 3 |
| rince | 3 | 0 | 1 | 1 |
| arenclissold | 3 | 0 | 2 | 1 |
| Drowze | 3 | 0 | 1 | 2 |
| tomdev | 2 | 0 | 1 | 0 |
| lazureykis | 2 | 0 | 2 | 0 |
| LRFalk01 | 2 | 0 | 0 | 1 |
| zzeniou86 | 2 | 0 | 0 | 2 |
| camero2734 | 1 | 0 | 1 | 0 |
| linstantnoodles | 1 | 0 | 0 | 1 |
| PhilippeChab | 1 | 0 | 0 | 1 |
| DiscreteObject | 1 | 0 | 0 | 0 |
| TheGr8OK | 1 | 0 | 0 | 0 |
| Amnesthesia | 1 | 0 | 0 | 0 |
| pulkit110 | 1 | 0 | 0 | 0 |
| drhops | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#142drhops2026-05-18 22:16SystemStackError: stack level too deep w/ graphql-ruby >= 2.5.12
- Issue#140TheGr8OK2025-07-02 15:33[Question] How do you usually handle deeply nested objects cache invalidation?
- Issue comment#139DmitryTsepelev2025-06-26 13:34[Question] Invalidating cache on the backend
- Issue comment#135zzeniou862025-05-22 13:01Stack Level Too Deep When NullStore
- Issue comment#135zzeniou862025-05-22 10:02Stack Level Too Deep When NullStore
- Pull request#137DmitryTsepelev2025-05-09 14:33
- Issue comment#138DmitryTsepelev2025-05-05 15:13[Question] Dataloader option
- Issue#138DmitryTsepelev2025-05-05 15:13[Question] Dataloader option
- Issue#138Amnesthesia2025-05-05 03:58[Question] Dataloader option
- Issue comment#136DmitryTsepelev2025-04-28 12:54Undefined method new_connections? in tracer.rb with graphql-ruby >= 2.3.11
- Pull request#137DmitryTsepelev2025-04-28 12:51
- Issue comment#136palexvs2025-04-23 04:58Undefined method new_connections? in tracer.rb with graphql-ruby >= 2.3.11
- Issue#136DiscreteObject2025-04-22 23:55Undefined method new_connections? in tracer.rb with graphql-ruby >= 2.3.11
- Issue comment#135DmitryTsepelev2025-03-01 10:02Stack Level Too Deep When NullStore
- Issue comment#135LRFalk012025-02-24 13:57Stack Level Too Deep When NullStore
- Issue comment#135DmitryTsepelev2025-02-21 15:34Stack Level Too Deep When NullStore
- Issue comment#134mgruner2025-02-20 19:33Add possibility to include and exclude arguments from generated cache key
- Issue comment#134DmitryTsepelev2025-02-20 15:00Add possibility to include and exclude arguments from generated cache key
- Issue#133DmitryTsepelev2025-02-20 15:00Possibility to filter out arguments from `path_cache_key`
- Issue comment#134mgruner2025-02-19 08:55Add possibility to include and exclude arguments from generated cache key
- Issue#135LRFalk012025-02-18 20:01Stack Level Too Deep When NullStore
- Issue comment#134mgruner2025-02-18 13:53Add possibility to include and exclude arguments from generated cache key
- Issue comment#134mgruner2025-02-14 11:05Add possibility to include and exclude arguments from generated cache key
- Pull request#134mgruner2025-02-14 11:04
- Issue comment#133DmitryTsepelev2025-02-13 16:05Possibility to filter out arguments from `path_cache_key`
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 71 stars here means stars gained during the window, not the repo's star count.