![]() SRCTREE-2729 Sourcetree does not display repository custom image at bookmarks.SRCTREE-2651 Switch to per-release release notes.SRCTREE-2494 Fix the path for a diff/merge tools in Preferences to update correctly.SRCTREE-2406 Fix the "Don't ask me again" checkbox to stop asking to download the LFS adapter when checked.SRCTREE-2399 Fix un-checking "Refresh automatically when files change" in Tools/Options/General to correctly change Sourcetree's behaviour.SRCTREE-6341 Fix Sourcetree crash when opening log window.SRCTREE-6371 Fix the current branch not being correctly selected after a UI refresh.SRCTREE-6427 Ensure null is not an outcome when calculating anonymous ids for analytics events.SRCTREE-6511 Correctly reference Askpass.exe when the Git Credential Manager for Windows fails. ![]() SRCTREE-6508 Correct running the diff tool when requested rather than the merge tool.SRCTREE-6479 Re-order the Welcome Wizard to align with the macOS version.SRCTREE-6476 Remove Atlassian account as a registration option.SRCTREE-6530 Only set the default username and email in Sourcetree's configuration when explicitly asked to in the Welcome Wizard.SRCTREE-6529 Fix the link to Analytics details in the revised Welcome Wizard.SRCTREE-6511 Correct the dependencies of Askpass.exe used when the Git Credential manager fails.SRCTREE-6571 Fix errors ith GitLab account creation and improve the labelling around Personal Access Tokens.SRCTREE-6568 Prevent showing git credential manager prompts if there's already one visible.SRCTREE-6549 Fix Diff/Merge Tool configuration not being saved during restarts.SRCTREE-6547 Fix being unable to re-open Sourcetree after minimizing.SRCTREE-6546 Support Email addresses as usernames for Bitbucket Server registration and accounts.SRCTREE-6593 Re-instate old commit-all behaviour.SRCTREE-6581 Further sanitizing URL encoded remote urls used during cloning.SRCTREE-6560 Add indicators for detached HEAD state to the sidebar.SRCTREE-6549 Fix the Preferences Diff/Merge Tool UI to correctly reflect changes in the configuration.SRCTREE-6353 Improved time-outs for detecting missing repository folders when re-opening tabs.SRCTREE-6625 Ensure Mercurial credential management for Bitbucket HTTPS remotes works without TLS 1.x.SRCTREE-6624 Remove the use double /s in the Create Pull Request URLs.SRCTREE-6629 Correct the wording of the analytics opt-in setting in the Tools/Options/General tab.SRCTREE-6620/ SRCTREEWIN-10957 Sanitize file names in Mercurial actions to avoid running potentially malicious ad-hoc hook commands.SRCTREE-6356 Stop resetting AllowModif圜onfigFiles to true on every re-start.You can use the git checkout command to undo changes you’ve made to a file in your working directory.SourceTree Release Notes SourceTree 3.0.15 Changes Git checkout -force BRANCH-NAME Undo Changes in your Working Directory When you run the following command, Git will ignore unmerged entries: git checkout -f BRANCH-NAME Basically, it can be used to throw away local changes. You can pass the -f or -force option with the git checkout command to force Git to switch branches, even if you have un-staged changes (in other words, the index of the working tree differs from HEAD). This is equivalent to running git branch with -f. If the BRANCH-NAME branch already exists, then Git resets the branch to START-POINT. If the BRANCH-NAME branch doesn’t exist, Git will create it and start it at START-POINT. The following command is similar to checking out a new branch, but uses the -B (note the captital B) flag and an optional START-POINT parameter: git checkout -B BRANCH-NAME START-POINT Checkout a New Branch or Reset a Branch to a Start Point This will automatically switch you to the new branch. To create and checkout out a new branch with a single command, you can use: git checkout -b NEW-BRANCH-NAME You have three options to handle your changes: 1) trash them, 2) commit them, or 3) stash them. Generally, Git won’t let you checkout another branch unless your working directory is clean, because you would lose any working directory changes that aren’t committed. To checkout an existing branch, run the command: git checkout BRANCH-NAME We can get the specific commit id’s by running: git log Checkout an Existing Branch To checkout a specific commit, run the command : git checkout specific-commit-id There are a number of different options for this command that won’t be covered here, but you can take a look at all of them in the Git documentation. The git checkout command switches between branches or restores working tree files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |