{"id":23760,"date":"2023-05-10T02:27:16","date_gmt":"2023-05-10T02:27:16","guid":{"rendered":"https:\/\/www.booksofall.com\/de\/?post_type=product&p=23760"},"modified":"2023-05-10T02:27:32","modified_gmt":"2023-05-10T02:27:32","slug":"git-notes-for-professionals","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/de\/git-notes-for-professionals\/","title":{"rendered":"Git\u00ae – Notes for Professionals"},"content":{"rendered":"

Chapter 1: Getting started with Git<\/h2>\n

Section 1.1: Create your first repository, then add and commit files<\/h4>\n

At the command line, first verify that you have Git installed:<\/p>\n

On all operating systems:<\/p>\n

git<\/b>\u00a0–version<\/p>\n

On UNIX<\/a>-like operating systems:<\/p>\n

which<\/b>\u00a0git<\/b><\/p>\n

If nothing is returned, or the command is not recognized, you may have to install Git on your system by downloading and running the installer. See the Git homepage<\/a> for exceptionally clear and easy installation instructions.<\/p>\n

After installing Git, configure your username and email address<\/a>. Do this before making a commit.<\/p>\n

Once Git is installed, navigate to the directory you want to place under version control and create an empty Git repository:<\/p>\n

git init<\/b><\/p>\n

This creates a hidden folder, .git, which contains the plumbing needed for Git to work.<\/p>\n

Next, check what files Git will add to your new repository; this step is worth special care:<\/p>\n

git status<\/b><\/p>\n

Review the resulting list of files; you can tell Git which of the files to place into version control (avoid adding files with confidential information such as passwords, or files that just clutter the repo):<\/p>\n

git add<\/b>\u00a0<<\/b>file\/<\/b>directory name\u00a0#1> <file\/directory name #2> < … ><\/i><\/p>\n

If all files in the list should be shared with everyone who has access to the repository, a single command will add everything in your current directory and its subdirectories:<\/p>\n

git add<\/b>\u00a0.<\/p>\n

This will “stage” all files to be added to version control, preparing them to be committed in your first commit.<\/p>\n

For files that you want never under version control, create and populate a file named .gitignore before running the add command.<\/p>\n

Commit all the files that have been added, along with a commit message:<\/p>\n

git commit<\/b>\u00a0-m “Initial commit”<\/p>\n

This creates a new commit with the given message. A commit is like a save or snapshot of your entire project. You can now push, or upload, it to a remote repository, and later you can jump back to it if necessary. If you omit the -m parameter, your default editor will open and you can edit and save the commit message there.<\/p>\n

Adding a remote<\/p>\n

To add a new remote, use the\u00a0git remote<\/b>\u00a0add command on the terminal, in the directory your repository is stored at.<\/p>\n

The\u00a0git remote<\/b>\u00a0add command takes two arguments:<\/p>\n

    \n
  1. A remote name, for example, origin<\/li>\n
  2. A remote URL, for example, https:\/\/<<\/b>your-git-service-address>\/<\/b>user\/<\/b>repo.git<\/li>\n<\/ol>\n

    git remote<\/b>\u00a0add origin https:\/\/<<\/b>your-git-service-address>\/<\/b>owner\/<\/b>repository.git<\/p>\n

    NOTE: Before adding the remote you have to create the required repository in your git service, You’ll be able to push\/pull commits after adding your remote.<\/p>\n

    Section 1.2: Clone a repository<\/h4>\n

    The\u00a0git clone<\/b>\u00a0<\/a>command is used to copy an existing Git repository from a server to the local machine.<\/p>\n

    For example, to clone a GitHub project:<\/p>\n

    cd<\/b>\u00a0<<\/b>path where you would like the clone to create a directory>
    \ngit clone<\/b>\u00a0https:\/\/<\/b>github.com\/<\/b>username\/<\/b>projectname.git<\/p>\n

    To clone a BitBucket project:<\/p>\n

    cd<\/b>\u00a0<<\/b>path where you would like the clone to create a directory>
    \ngit clone<\/b>\u00a0https:\/\/<\/b>yourusername@<\/b>bitbucket.org\/<\/b>username\/<\/b>projectname.git<\/p>\n

    This creates a directory called projectname on the local machine, containing all the files in the remote Git repository. This includes source files for the project, as well as a .git sub-directory which contains the entire history and configuration for the project.<\/p>\n

    To specify a different name of the directory, e.g. MyFolder:<\/p>\n

    git clone<\/b>\u00a0https:\/\/<\/b>github.com\/<\/b>username\/<\/b>projectname.git MyFolder<\/p>\n

    Or to clone in the current directory:<\/p>\n

    git clone<\/b>\u00a0https:\/\/<\/b>github.com\/<\/b>username\/<\/b>projectname.git .<\/p>\n

    Note:<\/p>\n

      \n
    1. When cloning to a specified directory, the directory must be empty or non-existent.<\/li>\n
    2. You can also use the\u00a0ssh<\/b> version of the command:<\/li>\n<\/ol>\n

      git clone<\/b>\u00a0git@<\/b>github.com:username\/<\/b>projectname.git<\/p>\n

      The https version and the\u00a0ssh<\/b>\u00a0version are equivalent. However, some hosting services such as GitHub recommend that you use https rather than\u00a0ssh<\/b>.<\/p>\n","protected":false},"excerpt":{"rendered":"