aboutsummaryrefslogtreecommitdiff
path: root/apps/servers/octopus/supergit/src/repo.rs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* supergit: add logo and rebuild READMEKatharina Fey2021-01-091-1/+1
|
* octopus: supergit: add interface to query specific store pathsMx Kookie2021-01-061-2/+2
|
* supergit: implementing tree parsingKaiden Fey2020-12-211-8/+24
| | | | | | | | | | | | This implementation is a bit weird, especially because it changes the API from what it was previously. This works, for now, but some of the relationships between types feel a bit bad. Especially that all queries have to go via the FileTree, and we can't just give out objects that represent some part of the tree that are then loaded when needed. For now this will work though. What's still missing is to turn a Yield::Dir into a new FileTree.
* octopus: refactoring & typed branch parsingMx Kookie2020-12-211-0/+98
This code is work-in-progress, and doesn't work on a repo that has a branched history. The issue here is that after handling a merge commit, keeping track of which commit to look at next is non-trivial. This solution tries to isuse a "skip" command on the walker, but this can accidentally skip commits, when two merges have happened in succession (maybe a bug with the impl, not the concept). But also, the actual merge commit seems to already be part of the norma history? So maybe we can ommit the merge commit explicitly, and simply return a new branch handle instead.