is a regex, it will search from the end of the previous -L This form will use the first line matching the given POSIX regex. If or is a number, it specifies an absolute line number Give zero or one positive revision arguments. Limited to a walk starting from a single revision, i.e., you may only Trace the evolution of the line range given by "," (or the function name regex ) within the In both cases +1 can be replaced with bigger number to get more line, or with regex to match the end of selected range.ĭetailed description from the docs: -L ,: (for line 15 of file path/to/your/file.txt) However, it's likely much simpler to use line number, like this: git log -L15,+1:'path/to/your/file.txt' The caveat is, if the line contains characters with special meaning in regex, you need to escape them. The meaning of argument to -L is "find the first occurrence of regex /the line from your file/, in path/to/your/file.txt and show the log regarding one line range starting at this point (meaning, just this line, but you could say +5 instead)". Fixed line would look like this: git log -L '/the line from your file/,+1:path/to/your/file.txt' Check the video below, showing the history of python development, to understand better what I’m talking about.Bomz gave the right option but with wrong syntax. Not really sure this animation alone brings any useful information but it’s definitely cool to see. Developers can be seen working on the tree at the times they contributed to the project. Directories appear as branches with files as leaves. Software projects are displayed by Gource as an animated tree with the root directory of the project at its centre. Git Temporal for VSCode has a similar goal: to allow you to quickly see the changes over time to a file or directory in your Git repository. Go back in time and see who did what changes when. Instead of visualizing the history of the repo, Git History helps you to quickly browse the history of files in any git repo. Dare to test your Git level with them and see if you can write the Git sequence of commands to reach the proposed scenario!. It helps you learn Git by proposing you to complete a sequence of Git exercises of increasing levels of difficulty. LearGitBranching.js is more than a playground to run and visualize Git commands. Similar, though less complete, this web is an example of how you could use D3 to visualize git histories. This time the commit graph is displayed horizontally. You can basically do the same as with Git Gud. Git Gud is a minimalistic web-based environment where you can write git commands and see their impact on an initially empty repository, with the sole purpose of “getting good” (I guess this is why they named the tool Git Gud).Īnother learning environment is Git School. They are basically an online environment where you can type sequences of Git commands and the tool renders a visualization to help you understand what’s going on in response to your commands Git Gud Tools whose purpose is to help you learn how Git works. This means that you can use that same GitUpKit framework to build your very own Git UI. GitUp itself is built as a thin layer on top of GitUpKit. And serious speed as well (they claim to render the entire graph of 40,000 commits for the official Git repo in less than a second).Įven better, GitUp is free and entirely open source. To top it off, in the same repo you’ll find GitUpKit, a reusable generic Git toolkit. Any change you make, large or small, even outside GitUp, is immediately reflected in GitUp’s graph. GitUp lets you see your entire labyrinth of branches and merges with perfect clarity. It’s a very interesting option for students, educators and non-profits as, beyond a free plan, they offer a pro account to all of them plus a large number of educational resources to learn Git. Among them, a visual commit history that includes also a drag-drop functionality. It comes with a large number of features and integrations. GitKraken is one of the most well-known Git clients. Gmaster is still free so give it a try (and give some feedback to the creators!). You are free to use these visualizations to get an overview of the state of the project and then move on to a more classical text diff/merge for the fine-grained details. Obviously, nobody forces you to everything at the graphical level. You can, for instance, also perform visual merges and visual diffs. The representation also helps identify the commits with more changes at a glance too.īut this is not the only useful visualization. To begin with, you can use its branch explorer to navigate your repository, checkout branches, diff and merge from this view. It integrates a number of different visualizations. Gmaster shows a strong commitment to being as visual as possible and not just a GUI wrapper on top of the Git command line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |