![]() And, if you don’t want to, we’ll still be friends. No obligations, of course, if you decide to. If you’re interested in downloading the GitKraken Git GUI client and taking it for a spin, please do me a favor and use my referral link to get started. If you need any help or have any questions, please feel free to reach out directly. I’ll be posting more “how to” articles for using the GitKraken Git GUI in the near future, as well as accompanying videos for each post (the video for this will be coming next). You must “push” them to the remote repository to make them available to others. Though a commit seems similar to saving a file, there are different aims behind. One thing to keep in mind (we’ll go over this in the next post in the series) is that these changes are still ONLY AVAILABLE TO YOU. A commit tells Git that you made some changes which you want to record. If you look closely in the last screenshot above, you’ll see that I already have changes that are “unstaged” that I’ll be “staging” and “committing” to make this blog post go live. That’s it! You’ve now committed your changes, and the process can start over with the next set of changes you need to make. Once you have entered a message (and this message can be as short as a single character, or much more polished), the green, “Commit changes to files”, will become enabled -Ĭlicking the, “Commit changes to files”, button will take the staged files, commit them to your local repository, and add a line to the commit history graph in the middle of the window. Personally, I generally only use the “description” for my commit messages. You can use either one, or both, based on how you like to format your messages. Git, and by extension GitKraken, allow you to have a “summary” and “description” for a commit. Once you have your changes staged the way you like, now you must supply a commit message. ![]() The very first thing you need to do before you can commit, is to stage your changes! In this post, I’m going to show you how to commit those changes to your repository. Easy as that You are now a master of squashing commits using the legendary GitKraken Git GUI Additional Resources. In my previous post, “ GitKraken Git GUI How-To: Add & Remove Files”, we went over how to add and remove (stage and unstage) changes using the GitKraken Git GUI application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |