| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
not implement the crazy sorting feature found in git-for-each-ref though
|
|
|
|
| |
file. This removes a git command invocation
|
|
|
|
| |
SymbolicReference.from_path creates only symbolic refs. This change was not detected by a test, hence there is room for improvement on the testing field
|
|
|
|
| |
reflog support. This should be manually implemented though for more performance, what it does is relatively easy
|
|
|
|
| |
only which is equivalent to waiting for an operation to finish completely. Now we parse the stream manually, allowing to retrieve progress information as soon as it happens
|
|
|
|
| |
as sha, even if the passed in id was a ref. This is done to assure objects are uniquely identified and will compare correctly
|
|
|
|
| |
a convenient shortcut to using the classes manually
|
|
|
|
| |
all parameters to be used. The test would not test everything either, and I would consider this a bug that slipped through
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* remotes:
Finished all push tests I could think of so far. More error cases should be studied, but they would be hard to 'produce'
Intermediate commit with a few added and improved tests as well as many fixes
Implemented PushProgress and PushInfo class including basic test cases. Now many more test-cases need to be added to be sure we can truly deal with everything git throws at us
Added frame for push testing and push implemenation
Another attempt to make fetch emit progress information, but in fact its 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
Added repo.refs for completeness (as remote.refs is there as well and quite nice to use)
Tried to use shallow repository - this works in case it is remote, but 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
Fixed bug when listing remotes - it was based on references which is incorrect as it cannot always work
FetchInfo class is not a subclass of Remote class anymore, as more classes are to be added it cluttered up the view and made things more complex as well
IterableList: added support for prefix allowing remote.refs.master constructs, previously it was remote.refs['%s/master'%remote]
tag handling tests finished, unfortunately there is not yet a rejected case, but it will assuambly follow with the push tests
Implemented handling of FETCH_HEAD and tags, some test cases still missing dealing with deletion and movements of remote tags ( which in fact is discouraged, but we should be able to deal with it, shouldnt we ;)
Added special cases to test that shows we cannot yet:
Added remote stale_refs property including test, tested new remote branch handling and deletion of stale remote branches
renamed remote_branch to remote_head, improved errror message
Added non-fast forward test case, fixed parsing issue caused by initial line stripping
implemented test for rejection handling and fixed a bug when parsing remote reference paths
Added testing frame for proper fetch testing to be very sure this works as expected. Plenty of cases still to be tested
Reference._from_string will now create the appropriate type, not just the type of the actual class. This could result in a symbolic reference returned even though you technically requested a reference - this issue must still be addressed.
put _make_file helper method into TestBase class
|
| |
| |
| |
| | |
studied, but they would be hard to 'produce'
|
| | |
|
| |
| |
| |
| | |
many more test-cases need to be added to be sure we can truly deal with everything git throws at us
|
| | |
|
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
nice to use)
|
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
type of the actual class. This could result in a symbolic reference returned even though you technically requested a reference - this issue must still be addressed.
|
|/
|
|
| |
remote: prepared FetchInfo class to be returned by fetch and pull. About to implement tests
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* index:
index.add: Finished implemenation including through tests
When parsing trees, we now store the originan type bits as well, previously we dropped it
cmd.wait: AutoKill wrapped process will automatically raise on errors to unify error handling amongst clients using the process directly. It might be needed to add a flag allowing to easily override that
added head kwarg to reset and commit method, allowing to automatically change the head to the given commit, which makes the methods more versatile
refs.SymoblicRef: implemented direcft setting of the symbolic references commit, which possibly dereferences to the respective head
index.commit: implemented initial version, but in fact some more changes are required to have a nice API. Tests are not yet fully done either
actor: added __eq__, __ne__ and __hash__ methods including simple test
index.remove implemented including throrough test
Implemented index.reset method including test
IndexEntry is now based on a 'minimal' version that is suitable to be fed into UpdateIndex. The Inode and device information is only needed to quickly compare the index against the working tree for changes, hence it should not be that dominant in the API either. More changes to come
Added notes about git-update-ref
Refs can now set the reference they are pointing to in a controlled fashion by writing their ref file directly
Added TagRefernce creation and deletion including tests
Implemented head methods: create, delete, rename, including tests
refs: added create, delete and rename methods where appropriate. Tests are marked, implementation is needed for most of them
Added frame for IndexFile add/remove/commit methods and respective test markers
Added repo.index property including simple test, and additional ideas in the TODO list
Renamed Index to IndexFile, adjusted tests, it will only operate on physical files, not on streams, as Indices are not streamed by any git command ( at least not in raw format )
|
| |
| |
| |
| | |
index.checkout: added simple method allowing to checkout files from the index, including simple test
|
| |
| |
| |
| | |
we dropped it
|
| |
| |
| |
| | |
unify error handling amongst clients using the process directly. It might be needed to add a flag allowing to easily override that
|
| |
| |
| |
| | |
change the head to the given commit, which makes the methods more versatile
|
| |
| |
| |
| | |
commit, which possibly dereferences to the respective head
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* refs:
Added notes about git-update-ref
Refs can now set the reference they are pointing to in a controlled fashion by writing their ref file directly
Added TagRefernce creation and deletion including tests
Implemented head methods: create, delete, rename, including tests
refs: added create, delete and rename methods where appropriate. Tests are marked, implementation is needed for most of them
|
| | | |
|
| | |
| | |
| | |
| | | |
by writing their ref file directly
|
| | |
| | |
| | |
| | | |
Added RemoteReference deletion and test
|
| | | |
|
| | |
| | |
| | |
| | | |
marked, implementation is needed for most of them
|
| | |
| | |
| | |
| | | |
required to have a nice API. Tests are not yet fully done either
|
| | |
| | |
| | |
| | | |
commit: Fixed long-standing issue during message parsing that would fail to parse properly in case we were created from data. Also it would strip white space from the messages although it shouldn't
|
| | | |
|
| | | |
|
| |/
| |
| |
| | |
into UpdateIndex. The Inode and device information is only needed to quickly compare the index against the working tree for changes, hence it should not be that dominant in the API either. More changes to come
|
| | |
|
| |
| |
| |
| | |
TODO list
|
| |
| |
| |
| | |
files, not on streams, as Indices are not streamed by any git command ( at least not in raw format )
|