sethrobertson/gitbestpractices

Commit Often, Perfect Later, Publish Once: Git Best Practices

gitbestpractices's Issues

Link not working

in the paragraph, Do backups
" though see also discussions about custom backup techniques to ensure git consistency. "

this link: http://thread.gmane.org/gmane.comp.version-control.git/168699 is not working.

shows only "ArchivedAt Nothing found - bye"

Dead link to "Who Needs Process"

http://teddziuba.com/2011/12/process.html
is 404

Optimize Page for Mobile

Hey Seth — Thank you for writing this (man years ago!), I enjoyed reading it!

I noticed the page has some issues when I tried to read it on my phone, and I wrote a walkthrough for the couple of tweaks you could make to the HTML to make it more readable:

https://maxwellforbes.com/posts/fixing-mobile-page-layouts#gitbestpractices

No worries either way, of course, just thought I'd pass along in case you were interested.

Cheers,
Max

Does it have an open licence?

As in issue #5 , I'd like to translate this best practices (to Spanish). I think some others would like to do the same with their own language.

I think I'd be easy if you can put an open license like a Creative Commons, in this way we (who wants to translate) can work & share without the need of a explicit permission. Of course, if you prefer a closed license nice to be explicit on this.

Thanks in advance.

Why "[don't] use a branch argument to git pull or git fetch"

Hello Seth,

I would like it very much if you elaborated on a one of the Miscellaneous "don't"s, namely "use a branch argument to git pull or git fetch". I think I get what you mean, but I lack a strong argument to tell other people why not do it. I've also tried to google it, but didn't find anything, however a link to an existing explanation would be great, as well.

Thanks for the great guide!
Best regards
Marcin

French Translation

Hello,

Thanks for you work. I will share this document in my company. A lot of my co-workers don't speak english, so i wanna know if a french translation is planned or if i can help?

Thanks.

Dead link to "Pro Git branching models"

http://www.progit.org/book/ch3-4.html
Server not found

Bad Link

http://progit.org/book/ in the 'Do read about git' section

Also the https://github.com/SethRobertson/GitBestPractices/issues at the bottom could open in a new window.

Cheers

large binaries and LFS

Git LFS seems to be addressing the issue with big binaries in git. Perhaps it is worth a mention
https://git-lfs.github.com/

r10k

In the section about dividing up repos, you mention gitslave and submodules. Both have the pros/cons, but in recent history.. r10k has become invaluable for this.

I'd like to see you update http://sethrobertson.github.io/GitBestPractices/#divide with a mention of r10k.

readme hyperlink not secure

I found your website through google and it brought me to (https://sethrobertson.github.io/GitBestPractices/).

However, when I followed that article to this repo, I re navigated to the website via the url in the README.md file. The hyperlinks within link to (http://sethrobertson.github.com/GitBestPractices/) which gives a Not Secure message in the search bar on most browsers.