active 2025-04-30 → 2025-10-31 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 185 days from 2025-04-30 to 2025-10-31. Pushes: 184 total, peak 28 in a day. Pull requests: 77 total, peak 16 in a day. Issues: 68 total, peak 52 in a day. Comments: 3 total, peak 1 in a day. Stars: 2 total, peak 1 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
Recent activity
Latest issues, pull requests and releases
- Issue#31AndLOLGG2025-06-11 11:25TUS3.1 Som udviklingsteam vil vi konfigurere GitHub Actions til at køre automatiske builds og tests ved push til main, så vi undgår fejl i main branch”.
- Issue#39AndLOLGG2025-06-11 11:22TUS5.3 “Som udvikler vil jeg kunne tilgå en separat testserver med kontinuerligt deploy, så vi kan teste opdateringer i et stabilt miljø før produktionsrelease”.
- Issue#61AndLOLGG2025-06-11 11:21US 6.3 Som Product Owner vil jeg vide, at der bliver testet både manuelt og automatisk, så vi får fanget fejl så tidligt som muligt
- Issue#2AndLOLGG2025-06-10 12:21TUS1.2 Definér funktionelle krav + Beskriv forretningsbehov
- Issue#27AndLOLGG2025-06-10 12:19TUS1.4 “Som udviklingsteam vil vi beskrive ikke-funktionelle krav (f.eks. teknologi, deployment, UI-principper) for at sikre at alle krav fra kravstiller er opfyldt”.
- Issue#37AndLOLGG2025-06-10 12:18TUS5.1 “Som udvikler vil jeg kunne køre applikationen med en H2 in-memory database, så jeg kan teste funktionaliteten hurtigt uden at forbinde til produktion eller en ekstern database”.
- Pull request#115AndLOLGG2025-05-28 10:39
- Pull request#115AndLOLGG2025-05-28 10:38
- Pull request#114AndLOLGG2025-05-28 09:49
- Pull request#113MaxRytter2025-05-28 08:16
- Pull request#111MaxRytter2025-05-28 08:06
- Pull request#110MaxRytter2025-05-28 07:41
- Pull request#108mcmadsv2025-05-27 17:23
- Pull request#107mcmadsv2025-05-27 14:41
- Pull request#107mcmadsv2025-05-27 14:41
- Pull request#106mcmadsv2025-05-27 13:20
- Pull request#105AndLOLGG2025-05-27 11:44
- Pull request#104MaxRytter2025-05-27 05:43
- Pull request#104MaxRytter2025-05-27 05:43
- Pull request#103MaxRytter2025-05-27 05:33
- Issue#48mcmadsv2025-05-26 16:54US2.2 Som bruger vil jeg kunne se den samlede estimerede tid for et projekt, så jeg kan danne mig et overblik
- Issue#47mcmadsv2025-05-26 16:54US 2.1 Som bruger vil jeg kunne angive estimeret tid (i timer) på både tasks og subtasks, så jeg kan beregne samlet tidsforbrug
- Pull request#102mcmadsv2025-05-26 16:35
- Pull request#101AndLOLGG2025-05-26 14:23
- Issue#59mcmadsv2025-05-25 08:12US 6.1 Som Product Owner vil jeg være sikker på, at alle vigtige funktioner i systemet er testet, så vi undgår fejl i den færdige løsning
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.