Skip to content
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.

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

Suggest different Discord notification action #4003

Open
wants to merge 1 commit into
base: source
Choose a base branch
from

Conversation

watteja
Copy link
Contributor

@watteja watteja commented Feb 25, 2025

While the exercise description advises picking any action from the Marketplace that does the job, I found the inclusion of previous action to be misleading, as it is currently broken even for most basic functionality.

After using embarrassing amount of time to make sure the problem was not with me, I found an alternative that can create notifications identical to the one included in the screenshots (also much more robust, given its simplicity of implementation). See my own notifications for proof

custom_notifications

Ignore identical commit times for both notifications, that is not action's fault, but mine. I'm aware I shouldn't --force push, but that's outside of the scope of this PR

While the exercise description advises picking *any* action from the Marketplace that does the job, I found the inclusion of previous action to be misleading, as it is currently broken even for most basic functionality.

After using embarrassing amount of time to make sure the problem was not with me, I found an alternative that can create notifications identical to the one included in the screenshots (also much more robust, given its simplicity of implementation).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant