3 ms·

I understand this is supposed to be funny but when I saw it, I was just like "WTF...". Coincidentally, I did just start a very similar Github project myself yes

by abi 15y ago

I understand this is supposed to be funny but when I saw it, I was just like "WTF...". Coincidentally, I did just start a very similar Github project myself yesterday. If you're looking for a real boilerplate boilerplate, here it is: https://github.com/abi/boilerplate https://github.com/abi/boilerplate . Right now, it includes a meaningful .gitignore for people who use UNIX and a README.md with the MIT license body. It's really supposed to be just for my personal needs/dev environment but I hope it's useful for the others who were equally disappointed by the contents of origin post too.

zb 15y ago
It's much better to ignore the files generated by your own tools with a global exclude file than to add them to every project's .gitignore. git config --global core.excludesfile ~/.gitignore
- abi 15y ago
  It depends. It's often been with the case for me that since I'm an undergrad and a lot of my collaborators are not too experienced with Git that people don't have their global gitignores set properly. In this case, it's better to put the ignores along with the code that everyone's pulling from.
jamesbritt 15y ago
I found myself either re-typing or cutting and pasting so much common code for numerous projects in different languages that I took what started as a template generator for Monkeybars and spun it off to a standalone boilerplate generator. http://neurogami.github.com/rhesus/ http://neurogami.github.com/rhesus/ I called it Rhesus since it was to make pieces for Monkeybars. :) Yes, it includes a template for .gitignore. It also allows for importing boilerplate templates from git repos. It's one of those projects that evolves as I find I need this or that feature or behavior.
- abi 15y ago
  Sweet idea. You should try to make your usage documentation better (more concise and put it on the Github page) cos I'm having a hard time figuring out how to use it as well as the rationale behind each step.
  - jamesbritt 15y ago
    I started writng some docs since the api and such has settled down. I have plans for a screencast too.

by abi 15y ago

zb 15y ago

It's much better to ignore the files generated by your own tools with a global exclude file than to add them to every project's .gitignore. git config --global core.excludesfile ~/.gitignore

abi 15y ago
It depends. It's often been with the case for me that since I'm an undergrad and a lot of my collaborators are not too experienced with Git that people don't have their global gitignores set properly. In this case, it's better to put the ignores along with the code that everyone's pulling from.

jamesbritt 15y ago

I found myself either re-typing or cutting and pasting so much common code for numerous projects in different languages that I took what started as a template generator for Monkeybars and spun it off to a standalone boilerplate generator. http://neurogami.github.com/rhesus/ http://neurogami.github.com/rhesus/ I called it Rhesus since it was to make pieces for Monkeybars. :) Yes, it includes a template for .gitignore. It also allows for importing boilerplate templates from git repos. It's one of those projects that evolves as I find I need this or that feature or behavior.

abi 15y ago
Sweet idea. You should try to make your usage documentation better (more concise and put it on the Github page) cos I'm having a hard time figuring out how to use it as well as the rationale behind each step.
- jamesbritt 15y ago
  I started writng some docs since the api and such has settled down. I have plans for a screencast too.