dobtco / hubot Goto Github PK

can we scrap piper?

Do we want to add any pipedrive integrations?

How cool would it be if deploy screendoor-v2 immediately printed the first line of every commit merged to production to slack?

From @jrubenoff on August 19, 2016 19:28

Thought I'd throw out a few ideas I had for making Hubot an easier task manager / communication tool.

1. I'd like a reminder every weekday morning (in my time zone) to update what I'm working on. Ideally this would keep me honest.

2. When I'm reminded, I'd like to actively confirm that I'm working on the tasks I've labelled. Something like this:

   

3. When colleagues ask Hubot what I'm working on, I want them to see the last time I confirmed the list, so that they know how up-to-date my list is.

   

4. Like we discussed on Friday, it would be nice to have our own repo for our personal tasks, that don't make sense in other repos. (Example: "finish my peer reviews", "schedule a meeting".)

5. When adding a task from Hubot, I'd like to pick which repo to add it to: my own personal repo, dobtco/dobt, dobtco/screendoor-v2, etc.

Copied from original issue: dobtco/dobt#1757

From @ajb on June 15, 2015 17:8

Copied from original issue: dobtco/dobt#1221

so far I know that

a) user has to be given permission to deploy to protected production branch
b) user has to get 2 env vars added to heroku

Our custom error handler isn't firing even though github is returning a 422 error when andrew tries to deploy

Fix the error handler so we can figure out why andrew cant deploy

cf #9

@jrubenoff: Like we discussed on Friday, it would be nice to have our own repo for our personal tasks, that don't make sense in other repos. (Example: "finish my peer reviews", "schedule a meeting".)

cf #9

@jrubenoff: When I'm reminded, I'd like to actively confirm that I'm working on the tasks I've labelled. Something like this:

cf dobtco/repo_setup#1

• "Where is [USER]?"
• "What is [USER] doing?"
• "cal [Event] at [location] at [when]"

cf #9

@jrubenoff: When adding a task from Hubot, I'd like to pick which repo to add it to: my own personal repo, dobtco/dobt, dobtco/screendoor-v2, etc.

Sometimes, multiple people collaborates on a task. For example, JG, Aidan and I are working on the competitor "war document". One of us might be working on it now, another might tackle it later, and it might not be on the third person's list. But if I add todo_upcoming to the task, Hubot will think all three of us are working on it next.

How do we get Hubot to understand the task's position in each person's to-do list?

https://hackpad.com/DOBT-Internal-Todo-List-Proposal-y4K2EbFPgA3

cf #9

@jrubenoff: I'd like a reminder every weekday morning (in my time zone) to update what I'm working on. Ideally this would keep me honest.

We rely on chatops pretty heavily, so it seems prudent to treat this repo the same as any of our other important repos. It doesn't have tests, but it'd be nice to be able to deploy to heroku just by merging to master.

That might be a bad idea because devs are used to master just deploying to staging. We could even have a staging version of hubot up and running, that only listens to commands in a special slack channel, and then use hubot itself to redeploy hubot (which would merge master to a production branch)...but all that might be overkill.

Still, it sucks to have to install heroku toolbelt and use heroku deployment flow, because we don't use that for anything else. deployment should be standardized.

cf #9

@jrubenoff: When colleagues ask Hubot what I'm working on, I want them to see the last time I confirmed the list, so that they know how up-to-date my list is.

• how much do clients owe us?
• how much does [X] owe us?

It would be nice if you could ask Hubot for all the pull requests assigned to you across every repository, to make sure there aren't any semi-urgent tasks you're overlooking.