fix: correct slashcommands directory path (Fixes #1)#25
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the slash command deployment script to read command definitions from the correct directory (src/slashcommands) so deployments don’t fail due to a missing folder.
Changes:
- Fix
deploy-commands.jsto load command files fromslashcommandsinstead ofcommands.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| const commandsPath = path.join(__dirname, 'slashcommands'); | ||
| const commandFiles = fs.readdirSync(commandsPath).filter(f => f.endsWith('.js')); |
There was a problem hiding this comment.
PR metadata says “Fixes #1”, but Issue #1 is about adding a !time prefix command; this change instead addresses bounty board Issue #21 (Critical #1: deploy-commands.js references non-existent directory). Please update the PR title/description to reference the correct issue (or remove the auto-close keyword) so the wrong issue isn’t closed.
Pull Request Review — Issue #1✅ Requirements — FULLY MET
🟢 Code QualityThis is the cleanest, most minimal fix for issue #1 among all related PRs (#23, #24, #25, #32). What it does:
Why it's superior:
|
This PR fixes the directory path in deploy-commands.js by changing 'commands' to 'slashcommands'. Claiming issue #1 from the community bounty #21.