+[2016-03-30T23:30:55Z]VxJasonxVyou are basically only guarenteed to get that +[2016-03-30T23:31:13Z]VxJasonxVwhen viewing .md files in a git repository, GitHub will only render to that specification +[2016-03-30T23:31:50Z]VxJasonxVhowever, when using GitHub to write issues/comments, etc., there is also "GitHub Flavored Markdown" ( https://guides.github.com/features/mastering-markdown/ ) +[2016-03-30T23:33:12Z]VxJasonxVvanilla markdown doesn't do Inline Code ( `code` ) nor Code Fencing ( ```\nfunction foo()\n``` ). It does code blocks via 4 leading spaces. +[2016-03-30T23:33:34Z]shudonoh, i see
is there a place i can go to test the github wiki editor?
+[2016-03-31T00:14:32Z]scazanhello all +[2016-03-31T00:14:59Z]scazanWas wondering if I could get some advice on common practice of how to treat the master branch +[2016-03-31T00:15:18Z]scazanDo you all generally treat master branch as the latest stable version of an application? +[2016-03-31T00:16:27Z]scazanI currently work off of dev branch and master branch is my stable... but thinking about whether what I should be doing is making a branch for the current version and master representing the latest stable bleeding edge +[2016-03-31T00:18:48Z]tang^whatever !workflow works for you