Skip to content

active 2024-04-192024-04-23 (UTC)

Complete coverage26,720 / 26,720 hourly files (100%) · 2 absent upstream2023-08-152026-09-01 (UTC)
Events
54
Pushes
21
Pull requests
0
Issues
17
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 5 days from 2024-04-19 to 2024-04-23. Pushes: 21 total, peak 20 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 17 total, peak 17 in a day. Comments: 14 total, peak 14 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

ContributorContributionsPushesPRsComments
NicholasTanYY382100
soc-pe-bot5005
nus-pe-bot4004
nus-pe-script3003
nus-se-bot1001
soc-se-bot1001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#16nus-pe-script2024-04-23 05:22
    Order of DG not clear at the start of the DG, making the organisation slightly messy.
  • Issue comment#15soc-pe-bot2024-04-23 05:17
    Returning from method call in sequence diagram does not deactivate the activation bar in the DG
  • Issue comment#14soc-pe-bot2024-04-23 05:11
    Sequence diagram contains default bottom headers, not removed to follow official standards
  • Issue comment#13nus-pe-bot2024-04-23 05:04
    Not stated in UG that the name input cannot be too long and needs to be in 1 word.
  • Issue comment#12nus-se-bot2024-04-23 04:56
    Incorrect folder path example
  • Issue comment#11soc-se-bot2024-04-23 04:46
    Incorrect link to webpage containing jar file for download
  • Issue comment#9soc-pe-bot2024-04-23 04:25
    Inconsistency in error handling for duplicate tasks: Error not handled when tasks are added using addrepeattask command
  • Issue comment#8nus-pe-bot2024-04-23 04:14
    Difficult to read output from the terminal
  • Issue comment#7nus-pe-script2024-04-23 04:03
    No option to view all tasks that a certain user has on all days
  • Issue comment#6nus-pe-bot2024-04-23 03:51
    No clear purpose of having the command addtwdc
  • Issue comment#5soc-pe-bot2024-04-23 03:39
    addtwdc command is not registered as an actual command when full command is typed in
  • Issue comment#4nus-pe-script2024-04-23 03:27
    Misleading error message when deleting a task for the current user on a day with no tasks
  • Issue comment#3soc-pe-bot2024-04-23 03:15
    Entering different names for switching results in different error message, causing ambiguity in actual mistake made
  • Issue comment#2nus-pe-bot2024-04-23 03:02
    Adding user whose name might contain apostrophe or other special characters renders the name addition to be invalid
  • Issue#16NicholasTanYY2024-04-19 09:45
    Order of DG not clear at the start of the DG, making the organisation slightly messy.
  • Issue#15NicholasTanYY2024-04-19 09:40
    Returning from method call in sequence diagram does not deactivate the activation bar in the DG
  • Issue#14NicholasTanYY2024-04-19 09:38
    Sequence diagram contains default bottom headers, not removed to follow official standards
  • Issue#13NicholasTanYY2024-04-19 09:31
    Not stated in UG that the name input cannot be too long and needs to be in 1 word.
  • Issue#12NicholasTanYY2024-04-19 09:26
    Incorrect folder path example
  • Issue#11NicholasTanYY2024-04-19 09:24
    Incorrect link to webpage containing jar file for download
  • Issue#10NicholasTanYY2024-04-19 09:20
    Urgent command does not recognise tasks that are ongoing, no matter the type of the task
  • Issue#9NicholasTanYY2024-04-19 09:13
    Inconsistency in error handling for duplicate tasks: Error not handled when tasks are added using addrepeattask command
  • Issue#8NicholasTanYY2024-04-19 09:02
    Difficult to read output from the terminal
  • Issue#7NicholasTanYY2024-04-19 08:58
    No option to view all tasks that a certain user has on all days
  • Issue#6NicholasTanYY2024-04-19 08:50
    No clear purpose of having the command addtwdc

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.