active 2024-09-10 → 2024-10-12 (UTC)
Complete coverage26,725 / 26,725 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-01 (UTC)
Events
40
Pushes
0
Pull requests
0
Issues
27
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 33 days from 2024-09-10 to 2024-10-12. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 27 total, peak 18 in a day. Comments: 1 total, peak 1 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 |
|---|---|---|---|---|
| 3omeTING | 15 | 0 | 0 | 0 |
| aliciathl | 7 | 0 | 0 | 0 |
| foodwithmo | 3 | 0 | 0 | 1 |
| xnicro | 2 | 0 | 0 | 0 |
| kaijiie | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#14foodwithmo2024-10-06 12:04Ferry Company Class Diagram
- Issue#20aliciathl2024-10-06 07:40Task: UC-3 Title: Indicate Job Preference and Availability Description: Employee indicate preferred location, routes, datetime and availability into the system. Deadline: 6/10/2024 IC: Hui Li
- Issue#19aliciathl2024-09-30 07:06Task: Create a Sequence Diagram for Employee
- Issue#183omeTING2024-09-30 01:21M1 Report Part 2
- Issue#173omeTING2024-09-30 01:18First task on your group’s project board, you are expected to post the key points from your discussions (on Slack) that the team has done
- Issue#173omeTING2024-09-30 01:18First task on your group’s project board, you are expected to post the key points from your discussions (on Slack) that the team has done
- Issue#163omeTING2024-09-30 01:18second task is to set up your team’s wiki on GitHub. Provide an introduction of your group’s project and how your team intends to address the problem in your project. You should use the wiki page to document the updates of your project.
- Issue#163omeTING2024-09-30 01:18second task is to set up your team’s wiki on GitHub. Provide an introduction of your group’s project and how your team intends to address the problem in your project. You should use the wiki page to document the updates of your project.
- Issue#153omeTING2024-09-30 01:17Include your team members’ roles decided in point 3C in your GitHub’s Wiki and your Slack channel and pin the message to your team’s channel
- Issue#143omeTING2024-09-30 01:13Ferry Company Class Diagram
- Issue#13foodwithmo2024-09-29 15:40Task: UC-5 Title: View Assigned Schedule: Employees can view their current job assignments for the week on their landing page. Deadline: 29/9/2024 IC: Jin Yao
- Issue#13foodwithmo2024-09-29 15:39Task: UC-5 Title: View Assigned Schedule: Employees can view their current job assignments for the week on their landing page. Deadline: 29/9/2024 IC: Jin Yao
- Issue#12xnicro2024-09-29 15:32Task: Create a Sequence Diagram for IT Admin
- Issue#11kaijiie2024-09-29 15:31Task: UC-2 Title: Amend Job Description: The system allows the manager to make changes to a job Deadline: 29/9/2024 IC: Timothy
- Issue#10xnicro2024-09-29 15:16Task: UC-1 Title: Add New Account Description: IT Admin adds new staff and managers into the system Deadline: 29/9/2024 IC: Solikhin
- Issue#5aliciathl2024-09-29 15:03Background Research
- Issue#4aliciathl2024-09-29 15:03Client Interview Preparation
- Issue#3aliciathl2024-09-29 15:02Ferry Company User Requirements
- Issue#2aliciathl2024-09-29 15:02SDLC Framework
- Issue#9aliciathl2024-09-29 14:56Task: UC-4 Title: Reject Job Description: Employee rejects a job they are unable to fulfill Deadline: 29/9/2024 IC: Hui Li
- Issue#83omeTING2024-09-29 14:48M1 Report Part 1
- Issue#73omeTING2024-09-29 14:46Ferry Company Use Case Description
- Issue#63omeTING2024-09-29 14:42Ferry Company system workflow
- Issue#53omeTING2024-09-29 14:38Background Research
- Issue#43omeTING2024-09-29 14:37Client Interview Preparation
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.