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

feat(alerts): add custom-alert command for user-defined alerts #4481

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

Conversation

MicLieg
Copy link
Contributor

@MicLieg MicLieg commented Feb 3, 2024

Description

In this PR i've implemented a new ./gameserver custom-alert command.

This custom-alert command allows users to tailor LinuxGSM alerts to their precise needs and preferences, enabling more effective monitoring and communication of specific events, and enhancing the automation of tasks for increased efficiency.

When running the command ./gameserver custom-alert users will be prompted for a custom alert message:
prompt

The prompt can be skipped by running the command with a message as parameter ./gameserver custom-alert "Quick Custom Alert":
parameter

For even more customization a second parameter can be added to set a custom title./gameserver custom-alert "Quick Custom Alert" "Custom Title":
withtitle

Fixes #4480

Type of change

  • Bug fix (a change which fixes an issue).
  • New feature (a change which adds functionality).
  • New Server (new server added).
  • Refactor (restructures existing code).
  • Comment update (typo, spelling, explanation, examples, etc).

Checklist

PR will not be merged until all steps are complete.

  • This pull request links to an issue.
  • This pull request uses the develop branch as its base.
  • This pull request subject follows the Conventional Commits standard.
  • This code follows the style guidelines of this project.
  • I have performed a self-review of my code.
  • I have checked that this code is commented where required.
  • I have provided a detailed enough description of this PR.
  • I have checked if documentation needs updating.

Documentation

If documentation does need updating either update it by creating a PR (preferred) or request a documentation update.

Thank you for your Pull Request!

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.

None yet

1 participant