go-git - A highly extensible Git implementation in pure Go.

	Commit message (Collapse)	Author	Age	Files	Lines
*	*: Remove redudant err nil checks	Paulo Gomes	2023-05-11	1	-4/+1
\| \| \| \|	Signed-off-by: Paulo Gomes <pjbgf@linux.com>
*	plumbing: object, rename calculation uses too much memory	Javi Fontan	2022-03-30	1	-1/+7
\| \| \| \| \| \| \|	The size of the similarity matrix is not limited and can be quite big when lots of files are deleted and added in a commit. Signed-off-by: Javi Fontan <jfontan@gmail.com>
*	fix goreportcard warnings	Oleg Kovalov	2020-07-01	1	-3/+3
\|
*	performed explicit conversions(needed)	vashish1	2020-05-08	1	-4/+4
\|
*	plumbing: exact renames detection could leave gaps in the changes	Miguel Molina	2020-05-04	1	-8/+4
\| \| \| \| \| \| \| \| \|	This fixes an issue where exact renames detection could leave gaps with nil changes in the added and deleted change slices. That could lead to panics in the content rename detection and others if the user had set OnlyExact to true. Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
*	fix 32 bit build	Todd Neal	2020-04-27	1	-1/+1
\| \| \| \|	Discovered while building on a Raspberry Pi
*	plumbing: detect renames by hash and similar content in diff tree	Miguel Molina	2020-04-23	1	-0/+817
	This commit implements the rename detection algorithms used in the JGit implementation. Given a list of changes, additions and deletions are extracted and matched in two ways: - By exact hash content: all additions and deletions are grouped by the content hash and paired with the best match based on the file mode and file path. All the files that cannot be paired are kept as regular deletions and additions. - By similar content: a matrix of addition and deletion pairs with all possible combinations is created and scored by how similar the content is between both files as well as how similar the file path is. The pairs with the best score and whose score is equal or greater than a threshold are paired and turned into a rename. All the files that cannot be paired are kept as regular deletions and additions. DiffTree and DiffTreeContext will not return the changes with renames detected for compatibility reasons, although this will change in v6 so that detecting renames is the default behaviour. A new function DiffTreeWithOptions has been added to configure the parameters for the rename detection to control the score threshold, the limit of renames and whether to use similar content detection in the detection. More information: - https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit/src/org/eclipse/jgit/diff/RenameDetector.java - https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit/src/org/eclipse/jgit/diff/SimilarityRenameDetector.java - https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit/src/org/eclipse/jgit/diff/SimilarityIndex.java Signed-off-by: Miguel Molina <miguel@erizocosmi.co>