Referencing and #41 for emoji stuff.

@jtmichelson Can I get a review?

I'd like to refactor the ping command and get rid of the other Slack Crate we were initially using. That might go in this PR it's very smol and quick to do.

When a new member joins the workspace slack sends this event https://api.slack.com/events/team_join

Using this documentation https://api.slack.com/messaging/sending message a user on behalf of my account with some basic info introducing myself and inviting them to introduce themselves in intros and come to hangout

Others are welcome to work on this just run it passed Rhett so he knows what's getting sent on his behalf

SlackAPI can trigger a challenge to our AWS API when a reaction is left on a user's message. See here for Reaction Added documentation

I have added the subscription and slack will trigger this every time that a reaction has added.

1. Implement a way to respond to the reaction
2. Start with the :buns: reaction
3. If a message contains "buns" or the buns emoji, add the :buns: reaction.
4. Remove the message reply inbuns.rs after adding this logic.

When devilbot is handling an event, it checks accordingly to the event to see if it should respond. If it is a development stage and the event came from outside the test channel then the function returns. Resolves #54

@jtmichelson I would like a review on this. Upon review this should enter an acceptance testing phase where when this event fires the message will just be sent to my account rather than the user that fired the event. After I can confirm that is working then I can change it over to the username that is coming from the body and this can be merged

• [x] Amend README.md to reflect creation of a unified POSIX (Mac and LInux) setup instruction
• [x] Amend build-function.sh to automatically configure, build, and install requisite packages for rust and npm based on kernel/architecture.

In our Slack workspace, we should make a new Slack App similar to "Flameboi", maybe just copy the permissions over from that previous app. Then communicate in the #devilbot-dev Slack channel the new OAuth creds so we can configure API Gateway accordingly.

Use this documentation to make a method for ephemeral messages. This will be a reusable feature to post messages in channels that are only visible to the user that is passed in.

Link to Slack Documentation

Currently the only way we can generate an incoming webhook is through the SlackAPI website. This is not ideal because it limits the amount of channels and users we can interact with. We need to generate a webhook programmatically.

Example: Brandon wants to implement a safety feature in the workplace that detects profanity in the hangout channel. It would be a simple matter to let the bot post a message to the hangout channel when profanity is detected. However, Brandon is not a simple developer who settles for static messages. He is an Alpha Giga Chad who would like to implement a feature that DMs the user who posted profanity (now a dynamic situation) and insults them in private.

Implementing this feature would open DevilBot to many different channels that it listens to, and can react in those situations.

Resolves #3 #1 Confirmed the build-function.sh works on Windows in WSL2 Ubuntu 20.04 LTS. Amended the README.md to reflect the setup for Windows machines.

Standardize the contribution process for this project.

1. All PRs related to issues should have the first line of their body/description include the resolves keyword and what issue it is meant to resolve (e.g. Resolves #2 to resolve issue #2). This auto-links the PR to the issue.
2. Assign at least 1 other reviewer to your PR and get explicit approval before merging (See issue #7).
3. Put clear descriptions in PR bodies to help the reviewer understand all context of your changes. Adding testing details if required.
4. Add an overview of how to do a simple Git workflow for creating a pull request with a new branch for new contributors that may not have used Git before.
5. Brainstorm any other standards.

Main feature contribution: DevilBot will now watch the intros channel and reply to user's introductions

Supporting contributions: Chat Post Message now receives the tread timestamp as an Option param. Now able to receive all the replies from a message

So this is working but there are some things that I know there is probably a better way to do in rust. Specifically, I am not sure if the way I added an optional parameter to the request in chat_post_message.rs was the best way. I also think that message_event_handler.rs is getting cluttered with logic. I was thinking I should create a handler for messages in specific channels where it is necessary

@jtmichelson closes #51

DevilBot will keep track of every time an emoji is used in a message. When that emoji has been used (example) 100 times, it will send a message to the channel it was last sent in with the Emoji, its definition, and an example sentence.

Be sure to only count the message once if the emoji is used more than once in the message. Account for multiple different emojis in the same message.

Example: Croatia played like :buns: in the world :cup: today. I hope they take their :buns: back to Europe Should count buns and cup each once

DevilBot will reply to a thread if there is a reply to a message that contains Welcome to CodeDevils, AND the reply is in intros, AND DevilBot has not already responded to the thread. We only want devilbot responding to things that are actually intros and not responding more than once.

DevilBot should respond with some introductory information about itself

Placeholder ticket. This was requested by a new member as of this year who is now an officer. Probably just message the user a list of info about the workspace, or use postEphemeral to give the info they need

• Make DevilBot partially CD.
• Use AWS Code Deploy to deploy code via merged commits to the main branch of our remote repo.
• Remove perms for devs to deploy directly to the prod CDK stack.