Now, assuming you’re familiar with branching, I’m going to go ahead and show you how to do the following things with branches in GitKraken: If you’re new to branching, please make sure you’ve read that first. It is explained in my guide: ‘ What are ‘branches’?‘. Now that you’ve got your Kraken all nicely set-up, you probably want to know about Working with GitKraken for Windows.īefore reading this, I hope that you understand what you are trying to achieve with branching. This is the slightly more complicated route, but still easy enough, and easier than Tortoise. You have your SSH Key copied, now you just need to paste it in to GitLab as demonstrated below:. Lastly, hit the copy-to-clipboard button to the right of the ‘ SSH Public Key field’ and that’s all you need to do in GitKraken. Browse to File > Preferences > Authentication, hit the Generate button, and when it asks you where you’d like to store it, just choose somewhere that makes sense to you, I would choose my dev folder, as this holds all of my Git projects:.But GitKraken gives the terminal a run for it’s money here. I still think a couple lines of code in GitBash is nothing to complain about when setting up SSH, compared to Tortoise anyway. What if I didn’t have SSH setup from the terminal before-hand? Of course, the path you see will have YOUR username in it, not Regan (MY username). If you’ve followed my guide, Getting Started with Git CLI for windows (Git Bash), then you already have an SSH Key, and can simply follow this gif: NOTE: THIS IS NOT AN IMPORTANT STEP TO WORKING WITH GIT! This is for people who don’t like having to key in their username and password when using git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |