+ [2015-09-11T20:07:14Z] nedbat Nevik: yes :)
+ [2015-09-11T20:07:30Z] Nevik actually you can probably build very neatly onto that since it does the state tracking
+ [2015-09-11T20:07:43Z] Nevik just have to build your initial state with some manual tinkering
+ [2015-09-11T20:09:18Z] nedbat Nevik: yes, thanks for helping me to re-discover it :)
+ [2015-09-11T20:09:46Z] Nevik you're welcome. if you build something that works, lemme know, i'm interested in how it'll end up working

message no. 111482

Posted by pisto in #github at 2015-09-11T13:22:59Z

well honestly it doesn't seem it's happening right now, but I saw that happening a couple of days ago
+ [2015-09-12T01:34:21Z] Hilton https://github.com/hiltonjanfield/jquery.enhsplitter/network - those funky shaped arrows at the start (and the end) suggest that I really don't know what the hell I'm doing.
+ [2015-09-12T01:35:44Z] Hilton Which is pretty much true.
+ [2015-09-12T04:08:52Z] Wetmelon Anyone know if there's a way to restrict organization members to pull requests? It seems that if you give the members access to a repo, they can push directly to it no matter what. Would they have to fork it to accomplish what I want?
+ [2015-09-12T04:14:06Z] Hilton Wetmelon: As I understand it, that's how it works. It says right on the Github page for Collaborators that it gives push access to the repository. That setting is for co-developers that you trust.
+ [2015-09-12T04:14:29Z] Hilton ANYONE, however, can fork your public repository and send you a pull request with their changes.