Ask for help with the /ta-support command. Here are some examples:

• A session url and description of the issue are recommended parameters. Order doesn't matter.

  /ta-support http://sessions.thinkful.com/casey We tried push our code to github with git push, we expected to see a confirmation, but we got an error message (which we Googled) but don't understand.

• Cancel your support request with remove or cancel

  /ta-support cancel

If you are a registered mentor, you can claim tickets from students with the /ticket-next command (without arguments). (Want to get registered? Ask Casey or Wences)

• Dequeue a ticket silently with /ticket-next silent

If you are a registered mentor, you can sign up for notifications for the specific days and times (and channels, even multiple!) that you work. Support requests in your chosen time slots will mention you.

• Run the command with your days and mornings or afternoons (not optional), run this more than once, it's additive, to configure your week.

  /ticket-alerts monday wednesday fri afternoons

  /ticket-alerts tue thu mornings

  

• Enable all mornings or afternoons with a shortcut:

  /ticket-alerts afternoons

• Disable all notifications with off

  /ticket-alerts off

• View your current notification by omitting a parameter or with view

  /ticket-alerts

  /ticket-alerts view

• Without arguments, get a link to this readme!

• Get your slack username and id, or the channel id

  > `/ticket-help username`
  
  > `/ticket-help channel`
  

We would love to have you contribute! Fork the repo!

• The Slacks Slash Command API, and therefore parts of this app are not very RESTful. Slack can only makes POST requests in response to a command, and expects a 200 response, even if you want to show the user an error.

• The command keywords (like /ta-support) are only editable in the Slack App settings, and often the names differ from the routes they hit here.

• NodeJS
• MongoDB

• Clone the repo
• Run npm install
• Run mongod in another window
• Run npm test in another window (everything green?)
• Run npm start in another window to start the server

You can get pretty far writing tests, the Slack API is relatively straightforward, but it's a good idea to test it out manually with a real Slack workspace

• A Slack workspace and app that you control (I set one up exclusively for testing Slack Apps)
• ngrok for tunneling

• Create an .env file with SLACK_VERIFICATION_TOKEN=yourSlackVerificationTokenHere
• Start the server, npm start
• Run ngrok http 8080 in another window
• Create Slack commands through Slack's website with the url that ngrok gives you, for example:
  • Command: /ta-support
  • Request URL: http://12345678.ngrok.io/support