| Age | Commit message (Collapse) | Author |
|
|
|
proven now that this is not happening if stderr is being redirected. A test is in place that will most likely fail in case this ever changes
|
|
unfortunately, deepening the repository fails if the server is used. This is bad, but a workaround is to create another shared repo which pushes a changes that we fetch into our given repo. This should provide more output to properly test the fetch handling. Harder than I thought
|
|
incorrect as it cannot always work
|
|
are to be added it cluttered up the view and made things more complex as well
|
|
constructs, previously it was remote.refs['%s/master'%remote]
Added first simple test for push support, which shows that much more work is needed on that side to allow just-in-time progress information
|
|
but it will assuambly follow with the push tests
|
|
dealing with deletion and movements of remote tags ( which in fact is discouraged, but we should be able to deal with it, shouldnt we ;)
|
|
handle the FETCH_HEAD case and
handle tags
System needs to be adjusted to take the FETCH_HEAD info into account to cover the tags case
|
|
handling and deletion of stale remote branches
|
|
stripping
|
|
reference paths
|
|
expected. Plenty of cases still to be tested
|
|
remote: prepared FetchInfo class to be returned by fetch and pull. About to implement tests
|
|
there is a default argument. This feels inconsistent as the 'argument passer' wrapper function can be called with a function or a string as first argument depending on whether the client code was explicitly passing an argument or not. That ... sucks. Now test for that case specifically and fail with a proper assertion error. I don't like it, but what can I do ... .
Remote tests adjusted to use rw repositories instead. More tests to follow, and many api methods are to be implemented now these things can be tested properly.
|
|
operations more convenient, like repo.remotes.origin.fetch
|
|
simple tests
|
|
CHANGES updated to carry information about remotes and config
|
|
|
|
|
|
config: fixed issue that would cause it to abort reading if the file did not exist - this is valid now
Test does not work as the configuration parsing does not work as expected - this must be fixed first
|
|
|