Awesome, thanks for the detailed feedback.<p>- Great point on permissions. I&#x27;m certainly going to do some digging to see how many people get turned away by that level of access. I could definitely understand if people are cautious with that, as you were, because they should be!<p>- The prevention of commits to master all happens via GitHub&#x27;s new protected branches feature (they use Git hooks I believe). You&#x27;re right, preventing force push is part of it, but the other thing it can do is require status checks (PullApprove is just another status check) on all commits to your base branch -- meaning nothing can be directly committed to the base branch, but should instead run through a pull request. Pretty interesting stuff: <a href="https:&#x2F;&#x2F;github.com&#x2F;blog&#x2F;2051-protected-branches-and-required-status-checks" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blog&#x2F;2051-protected-branches-and-required...</a><p>- Thanks for sharing this one, I definitely wouldn&#x27;t have thought of that without experiencing it myself.<p>- I&#x27;m planning on building some settings towards this. The most basic one giving an option that approval statuses go back to &quot;pending&quot; on new commits. It could possibly get more specific, giving an option to ignore whitespace changes etc...<p>- Nice idea. I&#x27;ll throw this in the hopper.<p>Let me know if you have any other thoughts!