+[2016-12-15T22:27:04Z]nikivithats a pretty neat setup +[2016-12-15T22:27:10Z]nikiviwhat is that, I am curuous? +[2016-12-15T22:27:35Z]sonOfRaThat is SublimeText with a Solarized Dark Theme&Scheme +[2016-12-15T22:28:40Z]sonOfRaSublime Text, sadly, is not a free text editor. I purchased a license a few years back because I found the LaTeX editing tools that are available for it as a plugin to be the best way to edit LaTeX documents +[2016-12-15T22:32:19Z]sonOfRasolarized dark is something I try to use for everything, feels more comfortable on the eyes, no real flashy colors (except for the hot pink identifying changed files)
+[2016-12-15T23:57:00Z]VionerHey guys, I know I can set a template for Issue comment - like here: https://help.github.com/articles/creating-an-issue-template-for-your-repository/ But can I also create an issue title template? +[2016-12-16T09:47:00Z]corpsicledoes github do any deeper conflict resolving than git in itself does? +[2016-12-16T10:53:47Z]timwishey folks, any advice on the best way to use github projects? i like that issues can have descriptions and conversations around them, but "notes" can't. i could just immediately convert every new note to an issue, but that seems like i'm missing some advantage of notes. +[2016-12-16T11:35:46Z]multifractalHi. So as part of a larger over-arching project (BIG_PROJ), there are many sub-projects (thing1, thing2, thing3...), that require development in their own right. Should each of these have their own branch, under the repository BIG_PROJ? +[2016-12-16T11:35:58Z]multifractalOr should they each have their own repo?