Rene Pfeuffer 33037385e4 Handle unexpected merge results
It is possible that a git work tree is dirty directly after the clone
of a repository, eg. when files are not changed correctly due to bogous
.gitattribute files (though this is just a guess). In these cases a
merge might fail due to these dirty files and not due to merge
conflicts. Without this change such results lead to null pointer
exceptions, because result.getConflicts() is null.
2020-02-27 09:56:25 +01:00
2020-02-25 08:24:12 +01:00
2020-02-25 16:22:54 +01:00
2018-09-24 13:03:02 +02:00
2016-06-26 15:04:55 +02:00
2019-10-08 09:29:11 +02:00
2011-04-05 17:06:34 +02:00
2020-02-25 16:22:54 +01:00
2020-02-27 08:36:47 +01:00
2018-05-31 12:40:37 +02:00
2020-02-25 08:24:12 +01:00
2014-01-06 11:35:46 +01:00

SCM-Manager

This branch (default) is for the development of scm-manager 2.x. If you are interested in the development of version 1.x, please checkout the 1.x branch.

Description
The easiest way to share and manage your Git, Mercurial and Subversion repositories over http.
https://scm-manager.org/ Readme 177 MiB
Languages
Java 75.6%
TypeScript 19.6%
CSS 2.1%
HTML 1%
Groovy 0.4%
Other 1.3%