rogerdudler / git-guide Goto Github PK

If you change the default branch from master to gh-pages in the repo admin section, first load of the repo page will show the proper files and commits. No more need to use the branch dropdown every time.

What about use some static builder to better cross language changes in git-guide?

With Jekyll, for example, you should not take care about the code around the content. For example http://sass-guidelin.es use that.

:)

This applies to both the excellent guide and cheat sheet.

On "add & commit" section, the phrase "Tu repositorio local esta compuesto" should be "Tu repositorio local está compuesto"

Git for Windows download address changed to http://msysgit.github.io/

I want to know which software can get those picture.
Ps:thanks your guide , i like that style

'Git Succinctly' by Ryan Hodson @ http://www.syncfusion.com/resources/techportal/ebooks/git

I'm totally new to Git, so presumably I'm someone who this guide is aimed at.

Leaving aside that you say to download Git, but don't mention installing it (I made that assumption)...

First instruction in your guide says "perform a git init" – now I only know what that means from trying Git without knowing what I'm doing for a while. By "perform a", I think you mean "type these words into the terminal:"

So I guess my feedback is that the language you use in the guide assumes some prior knowledge of Git / the Terminal, neither of which I really have.

Obviously in years to come when I am a Git pro, I will look back at this message in shame! ;-)

Paul

http://www.wei-wang.com/ExplainGitWithD3/#

hello,Could I download the git-guide and add it to my website?
www.git.kim

Hello,
I am willing to translate this guide to Welsh for the people who would like that.

Hallo and thank you for that easy tutorial in so many languages.

I got an issue when start working on a new branch. I was not able to push it in RStudio (a normal git push worked), because the branch has no entry in the config file.
The command
git branch --set-upstream myBranch origin/myBranch
for branch myBranch solved this problem. Perhaps you can add this as the last command in the branching section.

Kind regards
Dirk

I am member of a working group of web accessibility here in Brazil, and we are moving our repositories to Github, and we need to have an accessible Git tutorial.
So, we like a lot of this tutorial and we want to contribute on it to improve the acessibility on it.
But I believe that to do it in the best way, we need first to be concentrated in one "html" file, and because of it I also suggested the improvement of the translation files.
What do you think?

As well as there being a graphical client for Mac, there's also a graphical client for Windows - I feel that's worth adding to the links & resources section.

Never really explain what "origin" is, but then go and use it in the Branching section. This is a rather unique term to GIT/DVC, so new people (maybe coming from SVN) will definitely get confused.

Link to git for Linux no longer works, 500 error.
The below link should work.

http://git-scm.com/download/linux

$ git push origin master
fatal: 'server' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

http://www.runoob.com/manual/git-guide/
I know i don't heav the server, I don't know how to create the server

There is no reference to the initial user and email setup (telling Git who you are):

$git config --global user.name "Your Name"
$git config --global user.email "[email protected]"

This node should be between "setup" and "create a new repository"

There is not a single graphical git client for Linux in the guide, so I suggest adding git-cola. Best free graphical git client that I know of for linux.

On "flujo de trabajo" section, the phrase "Tu repositorio local esta compuesto" should be "Tu repositorio local está compuesto".

On "reemplaza cambios locales" section, the phrase "(lo que seguramente nunca suceda ;)" should be "(lo que seguramente nunca sucede ;)"

Which is better to use ?

Ich habe für mich angefangen bisserl zu verbessern :-)
https://github.com/dehenne/git-guide

Jedoch gibt es einige Unklarheiten ^^
Einige Überschriften sind auch in:
text-transform: lowercase;

Falls gewünscht kann ich gerne ein Pull Request machen.

I commit my projects. It is update in the github. But not reflect in the web pages. So Git pull stop working suddently.

Hello,

Tower is now also available now for Windows. 😄 Maybe anyone want's to change it and create a PR.

👍

"В ибоих случаях git" need change on "В обоих случаях git"

"fazer o merge estes conflitos manualmente" should be "fazer o merge destes conflitos manualmente"

Many times I found myself looking for this option when I need to show changes between commits.

I think it'd useful for many users who read the git guide.

So we had something like git diff --name-only <source_branch> <target_branch>

When I performed the commands in this guide I ended in a cryptic error. As proposed on stackoverflow I performed git commit -m 'Initial Commit' --allow-empty directly after git init. Now it worked fine. Please do update the according slide to help other users. PS: I am using git version 2.14. Configuration was already set up by the admin of my organisation.

What do you think about find a new way to do the translation?
Instead of create a new HTML file for each language, we can create a json file or a po file to save the sentences, titles etc...
I am suggesting it because of the subject of the next issue that I will open now.

can you add that to this sheet "git push origin v1.0"?

You speak about tagging. But "git tag" creates only a tag local.

create a new branch named "feature_x" and switch to it using
git checkout -b feature_x
switch back to master
git checkout master
and delete the branch again
git branch -d feature_x
a branch is not available to others unless you push the branch to your remote repository

I think this section also must have merge command.

Recommending that git gui be added to the list of 'useful hints'

the cheat sheet lists "git pull" .. i think as described there its dangerous and will make the main beginner task (keeping in sync with remote code changes without necessarily adding any of their own) needlessly error prone.

Besides git add . (already opened as an issue) also add git add -A which stages files in higher directories in the same git repository. This is specially helpful in case of changes like rm

Hi, I'm Namwoo Kim from South Korea.

I already cloned your repository and finished my first translated document.
Need for Pull Request. and some Korean can help me to review the my translations.
Thanks.

"git push origin master" does not push the current branch to the "master" branch in the "origin" remote.
It pushes the local branch of the specified name to either a remote branch of the same name, or an alternate name if it is specified with the : form of the parameter.

I think you should use ：）to replace ；）

I am using Chrome in Windows 7, and the Chinese characters are displayed terribly.
The sans and serif are messed up together.

Would you please confirm the Font family settings in the web page?

Edited russian translation index.ru.html. There were MANY mistakes!
You can view it in my repository.

Bonjour,

En cas de doute, voir la doc officielle.

J'ai pas regardé dans les autres langues.

Sinon bravo pour ce guide !

It could have a last slide talking about the SVN integration.

git pull ~> git svn rebase
git push ~> git svn dcommit

I think it's important for who have to work with a SVN remote repo with the GIT features.

Hi,

I did not find any information on how this guide is licensed.

Writing on git introduction myself, I would like to use some of your images.

Would you consider adding a CreativeCommons License?

"Роджер Дублер" should be "Роджер Дудлер" or "Роджер Дадлер".

I teach both HS and university students (and even K-8, at times), and I'd feel more comfortable pointing them to this great resource if "Shit" weren't so prominent.

Changing it to "S**t" would not substantially impact the usefulness.

One thing that could make use and sharing significantly simpler would be a consistent and clear means by which to share direct links to specific sections. I've noticed https://rogerdudler.github.io/git-guide/#log works fine, but https://rogerdudler.github.io/git-guide/#replace-local-changes does not.

Hey @rogerdudler could you consider put the label of links translation on each natural language instead of english. I think it's very nice, when a person looks to the guide his language is automacally understood