forgejo

forks/forgejo

Fork 0

Commit graph

Author	SHA1	Message	Date
Martin Scholz	26718a785a	Change git.cmd to RunWithContext (#18693 ) Change all `cmd...Pipeline` commands to `cmd.RunWithContext`. #18553 Co-authored-by: Martin Scholz <martin.scholz@versasec.com>	2022-02-11 13:47:22 +01:00
6543	3043eb36bf	Delete old git.NewCommand() and use it as git.NewCommandContext() (#18552 )	2022-02-06 20:01:47 +01:00
zeripath	f1e85622da	Improve TestPatch to use git read-tree -m and implement git-merge-one-file functionality (#18004 ) The current TestPatch conflict code uses a plain git apply which does not properly account for 3-way merging. However, we can improve things using `git read-tree -m` to do a three-way merge then follow the algorithm used in merge-one-file. We can also use `--patience` and/or `--histogram` to generate a nicer diff for applying patches too. Fix #13679 Fix #6417 Signed-off-by: Andrew Thornton <art27@cantab.net>	2021-12-19 05:19:25 +01:00

Author

SHA1

Message

Date

Martin Scholz

26718a785a

Change git.cmd to RunWithContext (#18693 )

Change all `cmd...Pipeline` commands to `cmd.RunWithContext`.

#18553

Co-authored-by: Martin Scholz <martin.scholz@versasec.com>

2022-02-11 13:47:22 +01:00

6543

3043eb36bf

Delete old git.NewCommand() and use it as git.NewCommandContext() (#18552 )

2022-02-06 20:01:47 +01:00

zeripath

f1e85622da

Improve TestPatch to use git read-tree -m and implement git-merge-one-file functionality (#18004 )

The current TestPatch conflict code uses a plain git apply which does not properly
account for 3-way merging. However, we can improve things using `git read-tree -m` to
do a three-way merge then follow the algorithm used in merge-one-file. We can also use 
`--patience` and/or `--histogram` to generate a nicer diff for applying patches too.

Fix #13679
Fix #6417

Signed-off-by: Andrew Thornton <art27@cantab.net>

2021-12-19 05:19:25 +01:00

3 commits