Upon declaring a new incident create a new incident doc from the template.
Upon closing an incident extract the incident channel messages (and timestamps) into the doc

An incident was opened recently with a topic that exceed the 250 character limit. Fortunately everything else in the process still performed but it did result in the following error:

0.17.0/lib/slack/web/api/endpoints/conversations.rb:313:in `conversations_setTopic'
2021-10-26T13:35:07.395045+00:00 app[web.1]: 	from /app/bot/actions/slack_incident_actions.rb:26:in `block in open_incident'
2021-10-26T13:35:07.502640+00:00 app[web.1]: E, [2021-10-26T13:35:07.502564 #4] ERROR -- : Slack::Web::Api::Errors::TooLong: too_long

Get the bot to start a Google meet

How to reproduce

1. There is an existing incident that's at P2, say, that's been raised in an existing channel.
2. I use the /incident update command in the incident channel (incident_...) to change its priority to P1. The bot correctly posts an update in the incident channel.

Expected: The bot posts an update of the incident priority in the existing channel.
Actual: no update is posted.

Create a new object that can offer methods like send_message etc. that can be used throughout the app.

Sometimes people wonder how to use the bot. Perhaps it's worth having a /incident help command that messages the user with instructions on what to do

Tests are currently quite basic and definitely don't cover the full functionality. They need some love.

Right now the bot is limited to posting/update in two specific channels – this is far too static. It should be able to post in Slack channels depending on which service is currently impacted by the incident.

• run the test suite
• run the linter

Currently the bot will only work with a specific modal. In order to make in more generic we need to build functionality so it can accept a modal with n number of fields and handle different data types for each i.e. integer, string or even a slack handle.

Need to add a pull request template