Skip to content
GitHub Explorer

RellDoesCode/COSC412-SWE-FastTrack

View on GitHub ↗Related repositories →

active 2025-03-26 → 2025-05-06 (UTC)

Complete coverage26,387 / 26,387 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-18 (UTC)
Events
80
Pushes
50
Pull requests
0
Issues
27
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 42 days from 2025-03-26 to 2025-05-06. Pushes: 50 total, peak 40 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 27 total, peak 13 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
Eb-Ajisa505000
RellDoesCode27000

Recent activity

Latest issues, pull requests and releases

  • Issue#22RellDoesCode2025-05-06 14:13
    Create a storyboard for the front end
  • Issue#24RellDoesCode2025-05-05 03:59
    Write a report about the API used for the project
  • Issue#23RellDoesCode2025-05-05 03:59
    Create an ER diagram of the schema for the back end
  • Issue#17RellDoesCode2025-05-05 03:59
    Create the database for the project to use
  • Issue#18RellDoesCode2025-04-28 16:03
    Develop code for the front end
  • Issue#25RellDoesCode2025-04-23 15:12
    Identify the challenges we faced as a team and document it for the final report
  • Issue#14RellDoesCode2025-04-09 15:31
    Submit Sprint 2
  • Issue#10RellDoesCode2025-04-07 16:08
    Create use case diagrams
  • Issue#12RellDoesCode2025-04-06 20:45
    Identify database specifications and analysis
  • Issue#11RellDoesCode2025-04-06 01:09
    Create class diagrams
  • Issue#16RellDoesCode2025-04-05 04:40
    Create use case requirements
  • Issue#13RellDoesCode2025-04-05 04:40
    Complete appendix
  • Issue#27RellDoesCode2025-04-05 01:55
    Update the readme file with instructions on how to use the software
  • Issue#26RellDoesCode2025-04-05 01:55
    Upload the code for the project to the github repository
  • Issue#25RellDoesCode2025-04-05 01:54
    Identify the challenges we faced as a team and document it for the final report
  • Issue#24RellDoesCode2025-04-05 01:54
    Write a report about the API used for the project
  • Issue#23RellDoesCode2025-04-05 01:53
    Create an ER diagram of the schema for the back end
  • Issue#22RellDoesCode2025-04-05 01:53
    Create a storyboard for the front end
  • Issue#21RellDoesCode2025-04-05 01:52
    Write the final problem statement
  • Issue#20RellDoesCode2025-04-05 01:51
    Complete the project report
  • Issue#19RellDoesCode2025-04-05 01:48
    Find a method for collecting geodata from the user
  • Issue#18RellDoesCode2025-04-05 01:47
    Develop code for the front end
  • Issue#17RellDoesCode2025-04-05 01:46
    Create the database for the project to use
  • Issue#16RellDoesCode2025-04-02 01:07
    Create use case requirements
  • Issue#15RellDoesCode2025-04-02 01:06
    Create use case diagrams

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.