GitHubCommand: Use .followUp() instead of .reply() after delete

The SDK doesn't like it when you try to initiate two replies to the same interaction. Let's see if it works if we send a follow-up message.
LadybirdBrowser · Dec 18, 2024 · e8e50a6 · e8e50a6
1 parent 6e3af34
commit e8e50a6
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/src/commands/githubCommand.ts b/src/commands/githubCommand.ts
@@ -151,7 +151,7 @@ export class GithubCommand extends Command {
 
           if (result) {
             await interaction.deleteReply();
-            await interaction.reply({ embeds: [result] });
+            await interaction.followUp({ embeds: [result] });
             return;
           }
         }
@@ -165,7 +165,7 @@ export class GithubCommand extends Command {
 
       if (result) {
         await interaction.deleteReply();
-        await interaction.reply({ embeds: [result] });
+        await interaction.followUp({ embeds: [result] });
         return;
       }
     }
@@ -177,7 +177,7 @@ export class GithubCommand extends Command {
 
       if (result) {
         await interaction.deleteReply();
-        await interaction.reply({ embeds: [result] });
+        await interaction.followUp({ embeds: [result] });
         return;
       }
     }
@@ -263,6 +263,6 @@ export class ReviewListCommand extends Command {
     const descriptionList = descriptions.map(({ description }) => description).join("\n");
 
     await interaction.deleteReply();
-    await interaction.reply({ content: descriptionList });
+    await interaction.followUp({ content: descriptionList });
   }
 }