Skip to content

interactivereduction/run-detection

View on GitHub ↗Related repositories →

The way we detect when our system for interactive reduction should automatically perform a reduction and with what arguments we should do that.

active 2023-08-16 → 2024-04-02 (UTC)

Complete coverage27,404 / 27,404 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-29 (UTC)
Events
752
Pushes
194
Pull requests
169
Issues
16
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 231 days from 2023-08-16 to 2024-04-02. Pushes: 194 total, peak 32 in a day. Pull requests: 169 total, peak 14 in a day. Issues: 16 total, peak 2 in a day. Comments: 132 total, peak 9 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

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

ContributorContributionsPushesPRsComments
keiranjprice1012591544517
dependabot[bot]158810743
Pasarus8621179
codecov[bot]630063
github-actions[bot]111100

Recent activity

Latest issues, pull requests and releases

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