nhcarrigan/rondelle
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 6 Pull Requests 1 Actions Releases Activity

WIP: Initial bot prototype #7

Draft
hikari wants to merge 4 commits from feat/prototype into main
pull from: feat/prototype
merge into: nhcarrigan:main
Conversation 0 Commits 4 Files Changed 13
+4613 -13
hikari commented 2026-01-21 20:25:05 -08:00
Owner
Copy Link
Copy Source

Summary

  • Set up Prisma schema for pairing history with event support
  • Scaffold Discord bot with database connection and logging
  • Configure TypeScript for ES modules with top-level await

What's done

  • Prisma schema with ServerEvent and UserPairingHistory models
  • Discord.js client initialization
  • Database connection via Prisma
  • Logger integration with @nhcarrigan/logger

What's next

  • Implement /breakout command
  • Auto-create voice channels
  • Pairing history tracking
  • Smart grouping algorithm
  • /breakout stats command

✨ This PR was created with help from Hikari~ 🌸

## Summary - Set up Prisma schema for pairing history with event support - Scaffold Discord bot with database connection and logging - Configure TypeScript for ES modules with top-level await ## What's done - [x] Prisma schema with `ServerEvent` and `UserPairingHistory` models - [x] Discord.js client initialization - [x] Database connection via Prisma - [x] Logger integration with `@nhcarrigan/logger` ## What's next - [ ] Implement `/breakout` command - [ ] Auto-create voice channels - [ ] Pairing history tracking - [ ] Smart grouping algorithm - [ ] `/breakout stats` command ✨ This PR was created with help from Hikari~ 🌸
hikari added 4 commits 2026-01-21 20:25:05 -08:00
feat: scaffold TypeScript project 2352f45794 
- Initialize pnpm project with TypeScript support
- Add standard ESLint and TypeScript configurations
- Create basic src/index.ts with sample export
- Set up GitHub Actions CI workflow
- Add prod.env with 1Password references
- Configure .gitignore for Node.js projects

Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
chore: fix up the scaffolding 5003386577
feat: add Prisma schema for pairing history ce59bf47f9 
Add MongoDB schema with Prisma 6.8.2 for tracking:
- ServerEvent: events per server (coffee chats, study groups, etc.)
- UserPairingHistory: user pairing records per server
- PairingRecord: individual pairing entries with event context

This enables smart grouping that avoids recent pairings per-event.
feat: set up Discord bot scaffolding
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 48s
Details
7997c9f59d 
- Add Rondelle interface with discord client and database
- Add logger utility using @nhcarrigan/logger
- Add database utility for Prisma client instantiation
- Update index.ts with bot startup logic
- Update .gitignore to exclude prod/ build output
Some checks are pending
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 48s
Details
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/prototype:feat/prototype
git checkout feat/prototype
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/rondelle#7
Delete Branch "feat/prototype"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?