While GitHub is a great development experience and a great way to see how the DSC resources you are using are being worked on, this does not lend well to some operational deployment models. You will have to either clone the main PowerShell or DSC resources repository or keep up with all the available DSC resource repositories on GitHub. Then, once these are all cloned, you'll have to take the local copy and distribute it out to your target nodes or your DSC pull servers yourself. Sure, you can automate some of this and get a pretty good script going, but if this all feels like a solved problem that you shouldn't be worrying about, you are not alone. The Microsoft PowerShell Gallery addresses this issue.