Slacker is an attempt to organize and systematize our developer/customer support use cases into something that is easy to manage and measure, and also is welcoming of newcomers wanting to help participate on projects.
### Tasks
- [x] `index.ts` - move each api route into its own file
- [x] `index.ts` - move crons into their own files
- [x] `index.ts` - breakdown slack `message` event and move it to a separate file
- [x] `actions.ts` - move each action into a separate file
- [x] `blocks.ts` - move each block into a separate file, break it down
- [ ] `commands.ts` - there's just one command, use switch/case to handle all subcommands; each case must be its own function
- [x] general refactor - `octokit.ts`, `utils.ts`
- [x] `views.ts` - move the business logic separate from the actual view code
- [x] `views.ts` - move each view into a separate file
Refactoring the slacker codebase