revup VS deadshot

Revup does a good job of integrating tree-of-PRs workflows into GitHub, and is also designed so that one developer can use it in a way mostly transparent to reviewers or their colleagues. I _think_ that Revup + Reviewable.io would match much of the capabilities listed in the linked talk.

https://github.com/Skydio/revup

I recently left FAANG for a smaller company, and have had to make the jump from the wonderful world of stacked diffs back to the mess that is gjt. I’d highly recommend revup to anyone looking for a better interface; it’s essentially a stacked diff/patch set model built on top git/GitHub: https://github.com/skydio/revup

- Many more! see the README and documentation

You can pip install and upload your first changes in minutes. Check it out at https://github.com/Skydio/revup

Code is no place for credentials, secrets, SQL statements, or any kind of sensitive data. But everyone makes mistakes, and it's important to be able to catch human errors before they create real problems. It is impossible to manually monitor any organization's entire code base hoping to catch sensitive changes before they escape to live forever on Github. This is a problem every security team faces when dealing with product code. The Product Security team at Twilio needed an automated way to ensure that developers weren't accidentally adding sensitive data to code repositories and to flag sensitive changes for a security review. We knew we couldn't monitor all code manually. Our solution: an automated way to monitor GitHub repositories in real-time, catching any sensitive data at the pull request stage, flagging issues as well as changes to sensitive functionality for a manual review. Thus was born Deadshot – which we're happy to be releasing as open source today.