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

Allow user to specify activation string #10

Conversation

jamesgeddes
Copy link
Contributor

@jamesgeddes jamesgeddes commented Apr 28, 2022

Adds a new activation_message variable to allow users to specify which activation string they want take-action to trigger on.

Allows user to specify an activation string that aligns with other platforms. For example, Slack and Discord use / to denote a command, so user can specify /take or /mine if they prefer.

Provides back compatible defaults so as not to break existing installations.

Resolves #9

rename INPUT_MESSAGE to INPUT_CONFIRMATION_MESSAGE to be entirely unambiguous about the two messages being requried.
add INPUT_ACTIVATION_MESSAGE to env and replace hard coded .take for variable.
users already have inputs.message so renaming this to inputs.confirmation_message would break live. return var to original name.
@jamesgeddes
Copy link
Contributor Author

@bdougie I don't suppose you have had a chance to think about any feedback on this, have you? Thanks in advance!

Copy link
Owner

@bdougie bdougie left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for keeping it clean. Happy to add this.

@bdougie bdougie merged commit 7cba81f into bdougie:main May 12, 2022
@jamesgeddes
Copy link
Contributor Author

Thanks @bdougie!

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.

Allow user to specify activation string
2 participants