+ [2016-03-30T23:30:55Z] VxJasonxV you are basically only guarenteed to get that
+ [2016-03-30T23:31:13Z] VxJasonxV when viewing .md files in a git repository, GitHub will only render to that specification
+ [2016-03-30T23:31:50Z] VxJasonxV however, 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] VxJasonxV vanilla 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] shudon oh, i see

message no. 129404

Posted by VxJasonxV in #github at 2016-03-30T23:33:12Z

vanilla markdown doesn't do Inline Code ( `code` ) nor Code Fencing ( ```\nfunction foo()\n``` ). It does code blocks via 4 leading spaces.
+ [2016-03-31T00:14:32Z] scazan hello all
+ [2016-03-31T00:14:59Z] scazan Was wondering if I could get some advice on common practice of how to treat the master branch
+ [2016-03-31T00:15:18Z] scazan Do you all generally treat master branch as the latest stable version of an application?
+ [2016-03-31T00:16:27Z] scazan I 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