+ [9 years ago] VxJasonxV you are basically only guarenteed to get that
+ [9 years ago] VxJasonxV when viewing .md files in a git repository, GitHub will only render to that specification
+ [9 years ago] VxJasonxV however, when using GitHub to write issues/comments, etc., there is also "GitHub Flavored Markdown" ( https://guides.github.com/features/mastering-markdown/ )
+ [9 years ago] VxJasonxV vanilla markdown doesn't do Inline Code ( `code` ) nor Code Fencing ( ```\nfunction foo()\n``` ). It does code blocks via 4 leading spaces.

message no. 129152

Posted by TheHackOps in #github at 2016-03-30T05:35:08Z

VxJasonxV, Not if my repo is on it :(
+ [9 years ago] scazan Was wondering if I could get some advice on common practice of how to treat the master branch
+ [9 years ago] scazan Do you all generally treat master branch as the latest stable version of an application?
+ [9 years ago] 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
+ [9 years ago] tang^ whatever !workflow works for you