+[10 years ago]nedbatNevik: yes :) +[10 years ago]Nevikactually you can probably build very neatly onto that since it does the state tracking +[10 years ago]Nevikjust have to build your initial state with some manual tinkering +[10 years ago]nedbatNevik: yes, thanks for helping me to re-discover it :) +[10 years ago]Nevikyou're welcome. if you build something that works, lemme know, i'm interested in how it'll end up working
[01:59] <Leonarth> is this expected behaviour?
+[10 years ago]Hiltonhttps://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. +[10 years ago]HiltonWhich is pretty much true. +[10 years ago]WetmelonAnyone 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? +[10 years ago]HiltonWetmelon: 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. +[10 years ago]HiltonANYONE, however, can fork your public repository and send you a pull request with their changes.