Skip to content

fix: correct slashcommands directory path (Fixes #1) #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TrivCodez merged 1 commit into from
Apr 29, 2026
Merged

fix: correct slashcommands directory path (Fixes #1) #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/deploy-commands.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ const fs = require('fs');
const path = require('path');

const commands = [];
const commandsPath = path.join(__dirname, 'commands');
const commandsPath = path.join(__dirname, 'slashcommands');
const commandFiles = fs.readdirSync(commandsPath).filter(f => f.endsWith('.js'));
Comment on lines +7 to 8
Copy link

Copilot AI Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.

for (const file of commandFiles) {
Expand Down
Loading