active 2024-01-31 → 2024-05-23 (UTC)
Complete coverage26,429 / 26,429 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-20 (UTC)
Events
222
Pushes
56
Pull requests
0
Issues
26
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 114 days from 2024-01-31 to 2024-05-23. Pushes: 56 total, peak 6 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 26 total, peak 24 in a day. Comments: 10 total, peak 9 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| edup3 | 47 | 21 | 0 | 0 |
| nceballosp | 37 | 27 | 0 | 10 |
| Aquinter10 | 8 | 8 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#24nceballosp2024-03-30 21:26FR14: Chat view for interacting with the chatbot
- Issue#24edup32024-03-29 20:31FR14: Chat view for interacting with the chatbot
- Issue comment#16nceballosp2024-03-29 03:41FR10: Integration with emergency services
- Issue comment#14nceballosp2024-03-29 03:39FR08: Assistance schedueling appointments
- Issue comment#10nceballosp2024-03-29 03:29FR04: Understanding user's symptoms
- Issue comment#23nceballosp2024-03-29 03:19FR13: ChatBot UI
- Issue comment#12nceballosp2024-03-29 03:06FR06: Accessibility for users with disabilities
- Issue comment#11nceballosp2024-03-29 02:58FR05: Historical diagnosis tracking
- Issue comment#8nceballosp2024-03-29 02:50FR02: Contact information for medical care
- Issue comment#13nceballosp2024-03-29 01:28FR07: Guidande for users during input process
- Issue comment#18nceballosp2024-03-29 01:12FR12: Registration and authentication for users
- Issue#23edup32024-02-25 00:17FR13: ChatBot UI
- Issue#22edup32024-02-20 04:29PR03: The system should respond to user inputs within a reasonable time frame, ensuring a smooth and efficient user experience.
- Issue#21edup32024-02-20 04:29PR02: The system should be available for users at all times.
- Issue#20edup32024-02-20 04:28PR01: The system should be able to be used by multiple users simultaneously.
- Issue#19edup32024-02-20 04:28UR06: The system should provide the user with the option for a real doctor to check the conversation with the chatbot.
- Issue#18edup32024-02-20 04:28UR05: The system should provide the user with the option to chat with a real doctor instead of the chatbot.
- Issue#17edup32024-02-20 04:28UR04: The user interface should be intuitive, user-friendly, and accessible to individuals.
- Issue#16edup32024-02-20 04:28UR03: The admin should be able to inspect the conversations between the chatbot and the users.
- Issue#15edup32024-02-20 04:28UR02: The system shall be able to support user authentication.
- Issue#14edup32024-02-20 04:28UR01: The system could offer to schedule medical appointments for the user.
- Issue#13edup32024-02-20 04:27LDR02: The admin should be able to handle the scheduling of medical appointments.
- Issue#12edup32024-02-20 04:26LDR01: The admin must be able to manage the database of medical centers.
- Issue#11edup32024-02-20 04:26FR05: Users should be able to track and review historical health assessments and recommendations.
- Issue#10edup32024-02-20 04:26FR04: The system must be able to understand the user's symptoms.
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.