New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
creating a template #1
Comments
ya i think it's fine as it is now. it shouldn't be dfiferent. main thing is that iw ouldn't want to fork from a repo that will have a lot of bikeshedding commits or db-edit commits. plus, stuff like style guides are probably excessive for most badgeboards |
Should we remove index.html from here to avoid merge conflicts? |
Also, if we use "push / pull", all commits here (including README) would appear in every other repository. They could be reverted, but that's commit spam nonetheless. |
sure. that would be pretty cool |
They will create unnecessary merge conflicts every time people pull stuff from here. #1 (comment)
closing, I'll open more specific issues soon... |
See:
jshttp/jshttp.github.io#2 (comment)
We need some real data in this template (so people will have working template before they even change anything). And jshttp data is as good as any.
So I don't see how this repo would be any different from jshttp.github.io (apart from minor style changes there, and deployment instructions here).
The text was updated successfully, but these errors were encountered: