Skip to main content

Everyday Git Commands

Git is a free and open source distributed version control system and a great one as well! Easy branch creation and jump between branches are some of its greatest features and here are some common commands that I use most of the time, hope this helps.

Set global settings for user information

$ git config --global user.name "[name]"

$ git config --global user.email "[email address]"

Check status

git status

Clone a project and working with branches

$ git clone [https://repository-link]

$ git checkout [branch-name]

Creating a new branch

$ git checkout -b feature/[branch-name]

$ git checkout -b bugfix/[branch-name]

$ git checkout -b release/[branch-name]

Renaming an existing branch

git branch -m bugfix/[branch-name] feature/[branch-name] --> Long version of renaming a branch (from bugfix to feature in this example)

git branch -m {bugfix,feature}/[branch-name]--> Short version of renaming a branch (from bugfix to feature in this example)

Adding changes for commit

$ git add [file] --> This is for adding a single file, following 2 commands are adding all allowed changed files

$ git add -A

$ git add .

Committing and pushing

$ git commit -m "commit message"

$ git push

$ git push --set-upstream [remote] [branch-name]--> If the branch is newly created.

Changing the most recent commit message

$ git commit --amend -m "new commit message"

Pull, fetch and merge

$ git pull

$ git fetch

$ git checkout [branch-you-want-to-merge-into]

$ git merge [branch-you-want-contents-from]

Reset changes

$ git reset [commit]

$ git reset --hard [last-known-good-commit]

$ git reset --hard HEAD~1 -->Undo the last commit, do not keep the changes.

$ git reset --soft HEAD~1 -->Undo the last commit, keep the changes.

Show all ignored files

$ git status --ignored

Check local, remote and all branches

$ git branch

$ git branch -r

$ git branch -a

Delete a local branch

$ git branch -d feature/branch-name

$ git branch -d bugfix/branch-name

$ git branch -d hotfix/branch-name

Delete a remote branch

$ git push origin --delete feature/branch-name

Tag checking and creation

$ git tag

$ git tag -a [tag-name] -m "tag description"

$ git push origin [tag-name]

Start using SSH in a repository where I am currently using HTTPS

$ git remote set-url origin [email protected]:v3/rest-of-your-project-ssh-url

Stash changes

$ git stash -->Save the un-committed changes in a "stash". This will remove changes from working tree.

$ git stash list -->List the stashes

$ git stash apply -->Apply stash to working tree in current branch

$ git stash apply stash@{0} -->Apply the stash 0 - change the number in order to apply other stashes

$ git stash drop stash@{0} -->Remove the stash 0 from stash list - change the number in order to apply other stashes.

$ git stash pop stash@{1} -->Apply the selected stash and remove it from the stash list.

Show all commits of the current branch as well as the parent branch and its commits

$ git log --first-parent

Exit git log history

$ :q -->For exit

$ :h -->For help

Comments

Popular posts from this blog

How to fix Git push error: "RPC failed; curl 56 HTTP/2 stream 7 was reset send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly"

Problem Today I saw the following problem when I tried to push my changes to a Git server after doing some work for upgrading an Umbraco v7 project to v8.18.8.  Possible reasons After some investigations, it seems like this could be because of the following reasons; Git is not happy with the amount of changes that are being pushed into the server.  There are possible limitations on the server about the size/amount of files that you can push. Your internet connection is not good and stable enough. Your Git client's version is old. Solution options For me, the easiest option was connecting to another Wifi and trying again. Apparently, this option helped quite a few people, so it is worth giving it a try. Unfortunately, it didn't work for me. A bad internet connection wasn't an option for me either, as my internet is pretty fast (500 Mbps). Similarly, my Git client version was the latest version (git version 2.41.0.windows.3).  On StackOverflow, there were a lot of recommendat

How to use JQuery Ajax Methods for Async ASP.NET MVC Action Methods

Making repeatedly calls to async methods can be a nightmare. In this case, it makes sense to use 2 ajax methods, instead of one. Here is a simple solution to overcome this problem. See that  ajaxcalls   is emptied after the success response for the first ajax call and then the second ajax method is used to make one single call to the async action method. Hope it helps. View: @section Scripts{     < script type ="text/javascript">         var smartDebitObject = new Object();         smartDebitObject.MembershipNumber = $( "#MembershipNumber" ).val();         smartDebitObject.ProfileId = $( "#ProfileId" ).val();         smartDebitObject.FirstName = $( "#FirstName" ).val();         smartDebitObject.LastName = $( "#LastName" ).val();         smartDebitObject.AddressLine1 = $( "#AddressLine1" ).val();         smartDebitObject.Postcode = $( "#Postcode" ).val();         smartDebitObject

How to fix "Microsoft SQL Error SQL71564: Error validating element [USERNAME]: The element [USERNAME] has been orphaned from its login and cannot be deployed."

I needed to export a database in BACPAC format today in order to restore it somewhere else, and I encountered the following error. To resolve this issue, I deleted all of the users mentioned in the error log. After successfully creating the BACPAC file, I used it to create a new database with no problems. Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ One or more unsupported elements were found in the schema used as part of a data package. Error SQL71564: Error validating element [USER1]: The element [USER1] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER2]: The element [USER2] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER3]: The element [USER3] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER4]: The element [USER4] has been orphaned from its login and cannot be deployed. Error SQL71