ComputerScienceHouse/schedulemaker
View on GitHubA course database lookup tool and schedule building web application for use at Rochester Institute of Technology.
- Stars
- 66
- Forks
- 39
- Open beginner issues
- 0
- Indexed issues
- 51
- Avg merge
- 3h 44m
- Merged PRs (30d)
- 1
- Dominant language
- PHP
- License
- GPL-2.0
- Last GitHub push
- Apr 3, 2026
- Latest indexed
- Sep 15, 2026
- Contributing guide
- No contributing guide
- Code of conduct
- No code of conduct
- Beginner labels
- good first issue
-
backend feature request
ComputerScienceHouse/schedulemaker#17 · 3 comments · 0 reactions · 1 assignee ·
-
feature request pending RIT question
ComputerScienceHouse/schedulemaker#54 · 1 comment · 0 reactions · 0 assignees ·
-
pending work
ComputerScienceHouse/schedulemaker#56 · 2 comments · 0 reactions · 1 assignee ·
-
backend bug
ComputerScienceHouse/schedulemaker#64 · 4 comments · 0 reactions · 1 assignee ·
-
feature request
ComputerScienceHouse/schedulemaker#69 · 2 comments · 0 reactions · 0 assignees ·
-
bug pending work
ComputerScienceHouse/schedulemaker#75 · 1 comment · 0 reactions · 1 assignee ·
-
pending reproduction
ComputerScienceHouse/schedulemaker#79 · 2 comments · 0 reactions · 0 assignees ·
-
feature request pending work
ComputerScienceHouse/schedulemaker#81 · 2 comments · 0 reactions · 0 assignees ·
-
bug pending work
ComputerScienceHouse/schedulemaker#105 · 4 comments · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#106 · 2 comments · 0 reactions · 0 assignees ·
-
feature request pending work
ComputerScienceHouse/schedulemaker#111 · 0 comments · 0 reactions · 0 assignees ·
-
requires data import refactor
ComputerScienceHouse/schedulemaker#112 · 1 comment · 0 reactions · 0 assignees ·
-
pending reproduction
ComputerScienceHouse/schedulemaker#117 · 0 comments · 0 reactions · 0 assignees ·
-
requires data import refactor
ComputerScienceHouse/schedulemaker#124 · 0 comments · 0 reactions · 0 assignees ·
-
requires data import refactor
ComputerScienceHouse/schedulemaker#145 · 1 comment · 0 reactions · 0 assignees ·
-
pending reproduction
ComputerScienceHouse/schedulemaker#153 · 2 comments · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#157 · 1 comment · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#169 · 1 comment · 0 reactions · 1 assignee ·
-
Better README Open
ComputerScienceHouse/schedulemaker#174 · 1 comment · 0 reactions · 1 assignee ·
-
bug pending reproduction
ComputerScienceHouse/schedulemaker#175 · 1 comment · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#184 · 0 comments · 0 reactions · 0 assignees ·
-
feature request good first issue
ComputerScienceHouse/schedulemaker#186 · 0 comments · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#188 · 2 comments · 0 reactions · 0 assignees ·
-
pending work ux improvement
ComputerScienceHouse/schedulemaker#193 · 2 comments · 0 reactions · 0 assignees ·
-
UI Update Openpending work ux improvement
ComputerScienceHouse/schedulemaker#194 · 0 comments · 0 reactions · 0 assignees ·
-
ux improvement
ComputerScienceHouse/schedulemaker#195 · 4 comments · 0 reactions · 0 assignees ·
-
pending work ux improvement
ComputerScienceHouse/schedulemaker#200 · 0 comments · 0 reactions · 0 assignees ·
-
Search by Professor Openfeature request frontend ux improvement
ComputerScienceHouse/schedulemaker#203 · 0 comments · 0 reactions · 0 assignees ·
-
dev improvement pending work
ComputerScienceHouse/schedulemaker#205 · 0 comments · 0 reactions · 0 assignees ·
-
bug frontend ux improvement
ComputerScienceHouse/schedulemaker#207 · 2 comments · 0 reactions · 0 assignees ·
-
good first issue
ComputerScienceHouse/schedulemaker#217 · 2 comments · 0 reactions · 1 assignee ·
-
bug pending RIT
ComputerScienceHouse/schedulemaker#218 · 4 comments · 0 reactions · 0 assignees ·
-
dev improvement
ComputerScienceHouse/schedulemaker#222 · 0 comments · 0 reactions · 0 assignees ·
-
ux improvement
ComputerScienceHouse/schedulemaker#233 · 1 comment · 0 reactions · 0 assignees ·
-
good first issue ux improvement
ComputerScienceHouse/schedulemaker#247 · 0 comments · 0 reactions · 0 assignees ·
-
ComputerScienceHouse/schedulemaker#252 · 5 comments · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#253 · 5 comments · 0 reactions · 0 assignees ·
-
feature request frontend
ComputerScienceHouse/schedulemaker#254 · 1 comment · 0 reactions · 0 assignees ·
-
ComputerScienceHouse/schedulemaker#311 · 2 comments · 0 reactions · 0 assignees ·
-
ComputerScienceHouse/schedulemaker#312 · 1 comment · 0 reactions · 0 assignees ·
-
dev improvement
ComputerScienceHouse/schedulemaker#320 · 4 comments · 1 reaction · 0 assignees ·
-
dev improvement
ComputerScienceHouse/schedulemaker#327 · 10 comments · 0 reactions · 0 assignees ·
-
bug frontend
ComputerScienceHouse/schedulemaker#332 · 0 comments · 0 reactions · 0 assignees ·
-
backend feature request frontend
ComputerScienceHouse/schedulemaker#333 · 2 comments · 1 reaction · 0 assignees ·
-
bug frontend
ComputerScienceHouse/schedulemaker#335 · 0 comments · 0 reactions · 0 assignees ·
-
ComputerScienceHouse/schedulemaker#336 · 0 comments · 0 reactions · 0 assignees ·
-
feature request
ComputerScienceHouse/schedulemaker#338 · 0 comments · 0 reactions · 0 assignees ·
-
bug
ComputerScienceHouse/schedulemaker#344 · 3 comments · 0 reactions · 0 assignees ·
-
ComputerScienceHouse/schedulemaker#348 · 0 comments · 0 reactions · 0 assignees ·
-
ComputerScienceHouse/schedulemaker#349 · 0 comments · 0 reactions · 0 assignees ·