Skip to content

Overvault-64/Firebase-Godot-API

View on GitHub ↗Related repositories →

active 2023-12-092024-09-22 (UTC)

Partial coverage22,088 / 26,309 hourly files (84%) · 2 absent upstream · 4,220 failed, retryable2023-08-152026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
16
Pushes
5
Pull requests
0
Issues
3
Stars
2
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 289 days from 2023-12-09 to 2024-09-22. Pushes: 5 total, peak 4 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 3 total, peak 2 in a day. Comments: 6 total, peak 5 in a day. Stars: 2 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
Overvault-6412505
JapanYoshi2001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#3Overvault-642023-12-20 23:07
    `new_data_update` is not emitted when the change is a new key in the referenced path
  • Issue comment#2Overvault-642023-12-20 22:35
    How to get data from Realtime Database reference
  • Issue#2Overvault-642023-12-20 22:35
    How to get data from Realtime Database reference
  • Issue comment#2Overvault-642023-12-20 21:19
    How to get data from Realtime Database reference
  • Issue comment#3Overvault-642023-12-20 21:06
    `new_data_update` is not emitted when the change is a new key in the referenced path
  • Issue comment#4Overvault-642023-12-20 20:57
    RTDB: Queued update calls have incorrect argument order
  • Issue#4Overvault-642023-12-20 20:57
    RTDB: Queued update calls have incorrect argument order
  • Issue#3JapanYoshi2023-12-12 04:32
    `new_data_update` is not emitted when the change is a new key in the referenced path
  • Issue comment#2JapanYoshi2023-12-10 10:46
    How to get data from Realtime Database reference

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