Changed behavior of .burn command.
#1298
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ran `make format`
ajax146
requested review from
a team,
ajax146 and
dkay0670
and removed request for
a team
ajax146
added
Waiting for Review
Extension: Burn
PR: Want for next release
ajax146
approved these changes
May 2, 2025
ajax146
removed
the
PR: Want for next release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the
.burncommand now behaves like the.hugcommand, meaning it doesnt require mentioning a user to mark their message as a burn. replying to the message works. it still retains it's original behavior of marking the last message of a user as a burn when it is used as.burn @user.