Skip to content

Lethal-Org/ProgressiveDeadline

View on GitHub ↗Related repositories →

Deadline scales with quotas.

active 2023-12-172024-12-11 (UTC)

Complete coverage26,750 / 26,750 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
35
Pushes
11
Pull requests
0
Issues
4
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 361 days from 2023-12-17 to 2024-12-11. Pushes: 11 total, peak 4 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 4 total, peak 1 in a day. Comments: 4 total, peak 1 in a day. Stars: 0 total, peak 0 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
theRealCarneiro121101
LTyphoonFOX2001
ustaalon1001
rabbit-time1001
gesangtome1000
Dantoresco1000
RandomSynesthetic1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#1rabbit-time2024-12-11 20:15
    [BUG] Getting fire doesn't reset the deadline to it's original value
  • Issue comment#4LTyphoonFOX2024-02-04 20:43
    Deadline exception
  • Issue#4LTyphoonFOX2024-02-04 17:59
    Deadline exception
  • Issue#3gesangtome2024-01-28 02:50
    When the deadline is longer than 10 days, no monsters will spawn
  • Issue#2RandomSynesthetic2024-01-27 21:44
    [BUG] Stuck on day 1
  • Issue comment#1ustaalon2024-01-08 15:41
    [BUG] Getting fire doesn't reset the deadline to it's original value
  • ReleasetheRealCarneiro2024-01-05 17:34
    2.0.1
  • Issue comment#1theRealCarneiro2024-01-05 13:18
    [BUG] Getting fire doesn't reset the deadline to it's original value
  • Issue#1Dantoresco2024-01-03 00:58
    [BUG] Getting fire doesn't reset the deadline to it's original value
  • ReleasetheRealCarneiro2023-12-21 12:41
    2.0.0
  • ReleasetheRealCarneiro2023-12-18 16:22
    1.0.1
  • ReleasetheRealCarneiro2023-12-17 14:55
    0.0.0

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