![]() ![]() GitHub controls the approval process for the GitHub Student Pack. Student Pack FAQ How long does it take to approve the GitHub Student Pack? This may mean you need to update the primary email address for your account. If you don’t see Pro then this means GitKraken does not see a pack with the email address tied to your GitHub account. If the app sees the pack, you should see the Pro flag in the bottom right of the UI and you will be able to open private repos. When you sign in with GitHub, GitKraken Client will check whether your GitHub account has the GitHub Student Pack. Or you may login by navigating to the profile dropdown > Sign into a different account > Sign in with GitHub To sign in again, launch GitKraken Client and navigate to File Sign into a Different Account Sign in with GitHub Once GitHub has approved your pack, you must sign into your GitKraken account through GitHub 1 more time to enable Pro. GitKraken GUI is free and available for Windows, MacOS and Linux! Click here to download GitKraken GUI.□ Important: Once you get the pack, you must sign into your GitKraken account through GitHub one more time to enable Pro on your account. You should also only make resets to local commits that have not yet been pushed to a remote repo. And if you’ve accidentally made a hard reset but there were some things you wanted to keep - then you’re really in trouble. And all your resetted commit structure (which files and changes were associated to each commit),Ĭommit names etc are now lost in time and space in your repo. If you go forward with this, you’re probably now left withĪ whole lot of uncommited and unstaged changes. Imagine that you are trying to make a reset to a commit 20 commits behind the last one. In the examples above we have only resetted a single commit. Resetting can be a very destructive action if used improperly. The same thing goes for all the affectedĬhanges. Notice that all history after the “Added script.js” commit is now gone. This can really mess up your repo, so make sure to tread carefully The main difference is that the affected files now are unstaged.Ī hard reset is pretty much nuking the specified repo history. That you can either continue working on or discard.Ī mixed reset is pretty much the same thing as a soft reset. Script.js is now reset to it’s previous version, with a pending uncommited change There were 4 commits, nowĪll the changed files have also been uncommited and are now staged. I’ll explain the differences shortly.Īfter making a soft reset, notice that all commit(s) made after the commit we resetted to now are gone. In most scenarios you are fine with selecting Soft or Mixed depending on personal preference. Your choice will affect the state of the changes you are resetting. I am now given three options - Soft, Mixed or Hard reset. I start out by right clicking the commit I want to reset back to: I want to undo the last commit and go back in time to the previous commit, “Added script.js”, which I know contains the last working version The horror! But fear not, this is easily fixed. But only after I’ve made the last commit, I discover that I’ve accidentally I have for this demo created a repo with a few commits. Typo, bug etc that you want to edit or remove.Īnd in GitKraken this is of course only a few clicks away. Reset is a very neat feature in Git if you want to go back in time and make a change to one or several commits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |