#Sourcetree checkout upgrade#
SRCTREE-1910 Upgrade to Libgit2sharp to v0.24.0, libgit2Sharp.NativeBinaries to v1.0.185, LibGit2 to v0.26.0.SRCTREE-1911 Upgrade Squirrel.Windows to v1.7.6.SRCTREE-1912 Fixed the order of setting merge parents when applying diffs.SRCTREE-1913 Fixed not being able to delete Authentication credentials.SRCTREE-1943 Apply SourceTree brand to updated BugSplat crash dialog.Suspend file watcher on non-active tabs to improve performance.SRCTREE-1974 Allow commit selected in staging mode whenever there's something to do.SRCTREE-1976 Added checks to validate existing System Git/Hg configuration and re-use a good configuration rather than the previous behaviour of wiping and reconfiguring on every restart.SRCTREE-1996 Fix Bugsplat reported crash when selecting tree items and static analysis bug fixes.SRCTREE-1137 Fixed Jump To list in the LogView to refresh and include newly created tags.SRCTREE-1803 Fixed diff sometimes not showing within folders when using split-staging with treeview file listings.SRCTREE-1947 Added UI Automation IDs to FileListings.Triggered by updating SourceTree's Squirrel dependency above release 1.5.0 SRCTREE-2024 Provide a workaround for Squirrel.Windows issue 1075 and ensure shortcuts are recreated correctly after an in-app update.SRCTREE-2039 Add filtering to remote ssh URLs to prevent remote execution commands reaching Git or Mercurial.SRCTREE-2078 Fixed switching to system Git or Hg and adding an option to reset the system path.SRCTREE-2039 Set the default behaviour to not recurse over submodules.SRCTREE-2096 Updated to Hg 3.7.3+14 Atlassian patched 3.7.3.
#Sourcetree checkout how to#
Interested about Git tags? Check our guide on how to delete local and remote git tags.SourceTree Release Notes SourceTree 2.1.11.0 Changes You also learnt more about checking out the latest Git tags from your repository in case you have multiple tags. In this tutorial, you learnt how you can easily checkout tags on Git using the “git checkout” command. * bd6903f (branch3) first commit Conclusion * 7a9ad7f (HEAD -> latest, tag: v2.0, origin/master, master) version 2 commit You can execute the “ git log” command in order to make sure that you are actually developing starting from the new tag. That’s it! You have successfully checkout the latest Git tag available in a new branch. $ tag=$(git describe -tags `git rev-list -tags -max-count=1`)įinally, use the “git checkout” command to checkout the latest git tag of your repository. Then, retrieve the latest tag available by using the “git describe” command. $ git fetch -tagsĪs you can see, you retrieve multiple tags from your remote repository.
#Sourcetree checkout update#
In order to checkout the latest Git tag, first update your repository by fetching the remote tags available. In some cases, you may be interested in checking out the latest Git tag of your repository. Now you can start working on your branch starting from the tag you specified earlier. Make sure that the HEAD pointer (the latest commit) is pointing to your annotated tag. You can inspect the state of your branch by using the “git log” command. Using this command, you have successfully checked out the “v1.0” tag. In order to achieve that, you would execute the following command $ git checkout tags/v1.0 -b v1.0-branch Let’s say for example that you have a tag named “v1.0” that you want to check out in a branch named “release”. To fetch tags from your remote repository, use “git fetch” with the “–all” and the “–tags” options. Note that you will have to make sure that you have the latest tag list from your remote repository. In order to checkout a Git tag, use the “ git checkout” command and specify the tagname as well as the branch to be checked out. In this tutorial, we are going to see how you can checkout Git tags easily.
Tags are created in order to have references to release versions for example.įurthermore, tags are Git objects meaning that they can be checked out like you would check out a branch or a commit for example. When working with Git, it is quite common for developers to create tags in order to have reference points in your development.
0 kommentar(er)
