3 ms·
Taken in isolation, the poster's example seems silly. It's just a PR, right? We'll add some process to ensure people look at it in a timely fashion yada yada ya
by outworlder 8y ago
Taken in isolation, the poster's example seems silly. It's just a PR, right? We'll add some process to ensure people look at it in a timely fashion yada yada yada.
Ok, but what about _all these small tasks over there_? They may also be small, but you have to think about them, work on them. Every second you are working on them you are not adding any value. Your brain gets tired, it makes everything feel so difficult to do, increasing friction on all tasks.
One thing that can't be overlooked: deploying changes to bots should also be seamless and automated as far as humanly possible. Otherwise they too will fall behind.
- avitzurel 8y agobots are automatically deployed via github too. They are just lambda function behind an API gateway. The library that interfaces with the bots is the same thing, once it's updated ALL of the builds will automatically use that latest version.
- outworlder 8y agoDid you roll your own? I was looking for some usable bot frameworks or libraries for lambda, but I couldn't find anything. I don't really have the time budget to roll my own stuff from scratch(although contributing back would be feasible).
- avitzurel 8y agoYes. We rolled our own. We’re always looking to open source, trying to find the resources
- lozenge 8y agoGitHub API has a good Python wrapper, it is usually not too difficult to roll your own. In this sample you can probably get the file list without a Git repo checked out at all. The key is to make every event from GitHub feed into a "reconsider_pr" function that refetches all info on the PR, rather than keeping state and trying to minimise your API requests. However it looks like you could build this out of combining bulldozer & another bot from palantir, if you really want to go no code.