One particularly useful tool for keeping a clean commit history on a working branch is Git’s -interactive rebase option. Our teams pride themselves on a clean commit history - not only on our main branch, but also inside the working branches maintained by individuals. At PSPDFKit, we host all our projects on GitHub, and many of them inside our monorepo, which currently counts about 50 active contributors. It’s pretty neat for when you want to find someone to blame.For most developers, Git is the go-to version control system for their software projects.
If you want to see more information than just the author name and the date modified, just right click on the annotated area, go into View then select what you want to see. It does exactly what git blame does – but in a nicer, IDE-friendly way. That’s what they call it in Android Studio (and IntelliJ and possibly other JetBrains IDEs). Shouldn’t Android Studio provide some sort of functionality that works with this? Introducing Annotate This works great when you’re working from the command line, but it seems a bit too primitive to use when you have the power of an IDE. In this example you only see my name because apparently I’m the only one who last modified each line of this file at the same time (which likely means that this was when the file was created and it has not been updated since), but depending on the situation it could mention multiple authors, timestamps and short hashes.
You can see who last modified each line, when the change was made as well as the short hash of the relevant commit. You should see something this: Output of git blame If you’re not familiar with git blame, go ahead and try it on the command line: $ git blame - path/to/my/source/file It does pretty much what it sounds like: it lets you blame each line in a file to whoever last made changes to that line. If you use git in your software projects, you might be familiar with the git blame command.
0 kommentar(er)
