Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
Jonathan GrieveTreehouse Moderator 91,252 Points
Public repositories on Github
I want to work with a client project on Git to get some practical experience with using Git on a project.
To me that means using Github remote repository to practice with regular push and pull requests.
But I'm torn as to whether I want to pay the $7 a month (less for an international exchange rate) for one private repository and I'm scared as to what could happen if I make the repository public.
I could keep the repository off Github completely I suppose but then what's the point. I may as well just work as I normally have.
It's a WordPress project I'm doing so this would be a bold Git project for me. I've already had to deal with some scary warnings like
warning: LF will be replaced by CRLF in .htaccess.
What does that mean? It's not had any effect at all on my files.
If you are torn between pricing and private repository, consider looking at "GitLab" (sort of little brother to "GitHub"). If offers free public & private repositories and loads of other features.
LF and CRLF are whitespace characters (not visible by default in editors) that occur at the end of a line:
- LF - Line Feed on Unix Systems ("\n")
- CRLF - Carriage Return + Line Feed on Windows Systems ("\r\n" )
If you want to turn this warning off, use the git command:
git config core.autocrlf true
You can read more about this issue here.
John Steer-FowlerCourses Plus Student 11,734 Points
Making a Github repo 'public' will mean that anyone can find it and fork it to get the source files for themselves. This means that anyone would have access to your client's source files. I obviously don't know much about the site, but I would recommend not making anything public unless it's yours and you want to release it for everyone to use.
By all means you can pay the $7 to make private repos.
I would recommend finding a public repo and contributing to it to practice.
One of the Treehouse members created this repo a few days ago for people to practice on, why not fork it and have a go at making some pull requests?
I have contributed a few times on that repo and it's a good project to have some fun on.
I hope this helps