![]() ![]() ![]() ![]() That will keep the sanity on your project. For example, if you are working on the chat, don't edit any other part not tied to that change, like the replay tab or the find games tab. That allow me to only select certain part of your changes if not everything is finished, or revert a bad change easily. Later, you will be able to ask me to get your modification to integrate them inside the main repository.Įach change you made you be in his own commit.Ī commit is like a "save state" of your work. Making a fork means that you take a repository to make your own version. Or you can use the workbench (program interface) Once installed, tortoisehg add a new option to your right click context menu in windows. This tutorial only cover the basics and will not explain how to branch, remove some changes. You probably want to read some mercurial documentation if you are not familiar with versioning softwares. First, you need to create an account on bitbucket. THIS TUTORIAL IS VALID FOR ANY FAF COMPONENT : LOBBY, FA CODE, BLUEPRINT EDITOR, FEATURED MODS. We are using a repository on bitbucket for versioning. Coming from Mercurial this was a foreign concept.Īdded 12-27-2016 I also now understand that the unrefernced nodes are not actually deleted but are still in repository and can be accessed via commit ID and branch logs but not as easily as if they appeared on the graph.LINKS TO THE REPOSITORIES ON THE SECOND POST The reason 's answer wasn't clear to me is I didn't understand why I needed to create a tmp_branch because I didn't understand that without a reference to a commit node Git will lose access to, or effectively delete those unreferenced nodes. Deleting RegressTest will not lose any commits as they are already referenced by one or more other branch pointers. Then when I am done I can delete the RegressTest branch pointer and then checkout my current branch again. (Like mentioned) I can then use RegressTest to load any commit in the entire tree for testing purposes. ![]() So how do I do that with Git? The easiest way to do that is first commit any outstanding changes in my workspace and then to do a checkout of the ancestor node to a NEW branch name like RegressTest. I just want to temporarily reload my current workspace with a previous commit for testing purposes and I don't want to change or lose any previous commits. That means when I move my current branch pointer to somewhere else I lose all recent commits that are descendants. But with Git there MUST be a pointer to a node or one of its descendants for it to show on the graph. That is if I reload my workspace with a node 3 commits previous, then those three subsequent nodes are not only still reachable, they are also visible on the graph tree. When I make a commit in Mercurial the commit tree for the common use case is static. Unlike Mercurial, in Git if you move your current branch pointer back to a previous node and there is no other branch pointer referencing any of the descendant nodes then those nodes are no longer reachable and are effectively lost. Another basic confusion I had was that commits could exist in Git without a branch(node reference) to them. It is not (as the name branch implies) a connected set of commits or nodes. The fundamental thing I didn't understand was what Git calls a branch is really just a pointer or reference to a specific commit node(change-set). So I'm sharing it for others like myself coming from Mercurial and trying to use Git for the first time. Now with a better understanding of Git branches I understand my confusion when I asked this question. However it's also possible to open up the logs of sub folders or individual files to only see their revision history. If you then you will see the full revision history for the current branch. To open the log, right-click on a folder containing a repository (it will have a hidden subfolder called. The temporary branch that was created can also be deleted by right-clicking on its log entry and choosing Delete refs/head/tmp_branch. To go back to the latest revision of master again, simply right-click on it and choose Switch/Checkout to "master": Similarly to TortoiseHg, the active revision is highlighted in bold: If you want to revert back to a previous revision without affecting changes already committed, open the log, right-click on the appropriate revision and choose Switch/checkout to this. To revert back to a previous revision and discard subsequent local changes, open the log, right-click on the appropriate revision and choose Reset master to this. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |