![]() If you're unfamiliar with Git or the Terminal please feel free to read these articles that show you the basics and what you can use them for. Hope that this helps with your journey with the terminal or an CLI type interface. git config -global user.name 'Tarcisio Coutinho' git config -global user.email '' git config -global color.ui true: git config -global alias.s status: git config -global alias.c checkout: git config -global alias.b branch: git config -global alias.lol log -oneline -graph -decorate: git config -global merge. Now when you run git status you will see the following: Running the following three commands in the terminal will add the color options that I specified below. ![]() For example, untracked files I wanted to be "cyan" while my changed files were "yellow" rather than red (More of a personal preference rather than a general need). In the code snippet above I have added a color="status" section which fine tunes the color variations between the different statuses a file could be in during a Git commit. You could stop here and probably be completely happy with everything, however, I wanted to take this a little step further and allow for a little more color variation in order to see what changes were being made in the terminal. ![]() In my case all my terminal commands are "red" for modified and deleted files or "green" if they were added ready for commit. Git will now color the output it sends to the terminal. To turn on the default terminal coloring: $ git config -global color.ui true ![]() When the color setting for name is undefined, the command uses color.ui as fallback. Personally, I preferred to let the terminal do this work for me and thus turned to running a few terminal commands to add the lines of code that I needed. To enable git-shs prompt colors explicitly, set the color.sh config value to auto: git config -global color.sh auto Customize. List only local configuration entries (stored in. When the color setting for name is undefined, the command uses color.ui as. If you feel safer opening this file in your code editor of choice and adding the lines you can feel free to do that. For reading options: read only from the repository. added = green changed = yellow untracked = cyan In this file we will be adding the following lines of code. Then I stumbled across Cheat Sheets and figured out a way to get the terminal to work a little better for me.įirst, all the modifications that we're making are to the ~/.gitconifg file located in your root user directory on Mac. One pet peeve that I had was that my terminal text was always white on black and extremely hard to read. For the last year I have been forcing myself each day to use the terminal much more to get used to doing things without an interface. You can also configure it using the following config command: git config -global http.proxy :.Then, click the green button in the top right corner that says New SSH Key. Next, on the left-hand side, click SSH and GPG keys. Then, click on Settings in the drop-down menu. Log into GitHub and click on your profile picture in the top right corner. http proxy :. First, youâll navigate to where GitHub receives our SSH key.Les distributions de Git pour Linux et les systèmes POSIX sont disponibles sur le site web officiel de Git SCM.Working with Git in the terminal can be hard to read and navigate at times. Add the following setting to the http items of. GitHub provides desktop clients which include a graphical interface for the most common manipulations and an "an automatically updating command line edition of Git" for the advanced scenarios.
0 Comments
Leave a Reply. |