terite/pull-to-master

Protect your master branch from pushes.

pull-to-master's Issues

Only allow pull requests based on branch X

I'm not really sure what exactly this feature would look like, but it was mentioned that if you have two long-lived branches, master and production, basing your pull request on master could make cherry picking into production more difficult.

this needs to be investigated and fleshed out

Convert to mary poppins bot

pull request detection isn't very robust

Basically, this script just checks the format of the last commit message.

How does this hook interact with other hooks/services

What happens if a push is rolled back, do other services/hooks still get called?

What happens when something like TeamCity/Travis gets notified of a commit to master that's no longer there.

improve pull request copy

• Notify offending pusher (with @)
• note about git reset origin/master
• something about letting someone else review it.

Does updating refs/heads/master trigger a push?

If reverting the master ref triggers a push, and the previous ref wasn't a pull request either, there could be an infinite loop scenario.

This needs to be investigated.

Index page about setup and which user to add.

• Tell visitor to add GH_USER as collaborator
• Tell visitor to add {{host}}/webhook as webhook
• Link to project page.