Skip to content

CloudComputing-Arknights/Microservice4

View on GitHub ↗Related repositories →

This is a messaging microservice

active 2025-11-042025-11-30 (UTC)

Complete coverage26,606 / 26,606 hourly files (100%) · 2 absent upstream2023-08-152026-08-27 (UTC)
Events
12
Pushes
3
Pull requests
1
Issues
7
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 27 days from 2025-11-04 to 2025-11-30. Pushes: 3 total, peak 2 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 7 total, peak 5 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 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
liz466211310

Recent activity

Latest issues, pull requests and releases

  • Pull request#9liz46622025-11-30 21:55
  • Issue#8liz46622025-11-17 03:04
    Connect messaging front end page to back end
  • Issue#6liz46622025-11-17 03:03
    Align ER Diagram with message and thread model
  • Issue#5liz46622025-11-16 06:46
    Set minimum replica for all Cloud Run to 1
  • Issue#3liz46622025-11-16 06:46
    Update Messaging microservice to work better for direct messaging
  • Issue#4liz46622025-11-16 06:45
    Make asynchronous
  • Issue#5liz46622025-11-16 06:44
    Set minimum replica for all Cloud Run to 1
  • Issue#2liz46622025-11-16 00:08
    Create Messaging and Thread microservice endpoints

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.