Open bbengfort opened 8 years ago
@samgoodgame please assign yourself to this issue when you accept the team invite!
@bbengfort it appears as though as a team member, I only have read access; unless there's another way to assign the issue to myself, it appears as though I am unable. Screenshot:
(There's no checkbox that I can use to assign)
@samgoodgame strange - I'll look into it, but I've added you.
@samgoodgame ok, you should now have write access.
@bbengfort Awesome, I assigned it to myself. Thanks!
@bbengfort should I point the readthedocs site at our development or master branch? Master currently doesn't have much on it, but I'm not sure if you want to hold off posting develop until we release it/merge with master
I'd say post it to develop for now, and we can start having different releases of documentation with the next push to production.
On Fri, Aug 26, 2016 at 1:31 PM, Sam Goodgame notifications@github.com wrote:
@bbengfort https://github.com/bbengfort should I point the readthedocs site at our development or master branch? Master currently doesn't have much on it, but I'm not sure if you want to hold off posting develop until we release it/merge with master
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DistrictDataLabs/partisan-discourse/issues/20#issuecomment-242799246, or mute the thread https://github.com/notifications/unsubscribe-auth/AAth7ikNYEDR8HyNQbjDv3P5CN1ZV-8lks5qjyLvgaJpZM4JtrVe .
Ok-- it's currently visible at this URL:
http://partisan-discourse.readthedocs.io/en/develop/
The regular URL (http://partisan-discourse.readthedocs.io/) just links to the placeholder that we have in the master branch (that says "this is the future home of the PD documentation")
@samgoodgame has started the process of documenting our work. As a result of his pull request, I've given him access as a contributor to the repository. Thanks @samgoodgame!
We still have a couple of steps on this issue: