AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Sourcetree checkout branch1/4/2024 "Given that, perhaps a more productive approach would be to try and find an existing tool other than SmartGit that appears to handle this correctly / better for Git repositories. This works only for existing branches which is OK since GIT only stores useful data. BranchPath could be a list of commits' SHAs or a list or lines coordinates and colors. Note that with Git 2.23+, that would be git switch. That will make sure the local branch develop will push to, by default, the remote branch origin/develop. When the user clicks on a branch name, you can retrieve the BranchRefCommit which can be used to know the BranchPath and then highligth the associated lines. git checkout -b develop -track origin/develop. Associate each BranchRefCommit to BranchPathĤ. Associate each BranchRefCommit to branches names (i.e. Using internal variables (in SmartGIT) you could :Ī. Also with the info returned by GIT you are able to connect commits using colored lines, let's call these lines BranchPath.ģ. Using the info returned by GIT you are able to draw a label with the name of the branch to visualize on what commit the branch points to, let's call this commit the BranchRefCommit.Ģ. This post was inspired by this SourceTree answer that I wrote back in 2011."This in itself would be very useful IMO"ġ. I hope this post helped you to get your changes back on track, and remember: In this post, you’ve seen how to create a git branch with your current changes preserved and tagging along. Select the previous commit, and create a new branch…Īfter you’ve created the new branch, your unstaged uncommitted work will be waiting for you while you have checked out the new branch.įrom this point on, you can work as usual and stage & commit your changes.
0 Comments
Read More
Leave a Reply. |