PR's now required for the master and devel branches

[Edward K. Ream]

This is an experimental restriction. It can easily be removed.

I think requiring PR's for devel and master makes sense. They alert everyone of proposed changes before they take effect. The PR's themselves are a permanent record of changes.

Let me know if you have any considerations about this new policy.

Edward

[Mike Hodson]

I for one like it. I've messed up too much with my own private git, so pull requests to make any mergeable changes sounds quite good.

I've been quiet but definitely following progress; at some point I'll start using Leo again, but this whole leointeg thing seems very nice. 

Mike 

[Thomas Passin]

And after I said this is a good idea, I just accidentally merged my changes to VR3 to upstream/devel instead of origin/devel.  Grrr.  No harm done, I think, because these changes were the ones that start to add asciidoc rendering, and they work on my computer at least.  They don't change any other functionality that someone would be using.

But I had better make sure I know how to avoid this in the future.  I've been working with Git Extensions, and somewhere I didn't notice that it had changed my checkout branch from origin to upstream.