As the semester windows down I'd like to start collecting bugs and other UI i...
As the semester windows down I'd like to start collecting bugs and other UI issues that we can fix over the summer. Do we have a good place to put those? For example, right now there are 8 students here but the instructor page says 0 / 10, so that's clearly wrong.
Yes — TODOS.md at the repo root is already serving this purpose. It has a mix of feature ideas and bug reports, several with **Reported**: <date> lines. I'll add the instructor count bug there now.
Added. A few thoughts on the file going forward:
- It's getting a mix of bugs, polish items, and feature ideas — might be worth splitting into
## Bugs/## Polish/## Featuressections this summer so you can triage by category. - Adding
**Reported**: <date>consistently (some older entries don't have it) makes it easier to see what's been sitting longest. - For the count bug specifically: if you can grab which page (
/facilitator,/display, the activity overview?) and the meeting slug next time it happens, that'll save investigation time later.
No, the 0 is fine; at that point it looked like nobody had submitted anything. It's the denominator that's off. We need a reliable way to track the number of students with recent page activity.
Updated. The entry now captures three things: (1) denominator should be "present students" not roster, (2) need a recent-activity signal to drive that, and (3) the 10 may already be double-counting (multiple tabs/sessions per user) — worth checking whether the counter dedupes on user ID.
Your task
First, run git status, git diff, and git log --oneline -10 to understand the current state.
Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.
Single change to TODOS.md — no debugging statements, no untracked files. Committing.
Committed as 4d34ef4. Branch is 1 commit ahead of origin/main — not pushing without your say-so.