alpha
Login
or
Join now
alice.pds.demo.boltless.dev
/
core
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
2
Pulls
1
Pipelines
core
/
knotserver
/
git
1 folder
7 files
at
b5fe3db418cde45351c1ede0c6f10aebea5eade6
Anirudh Oppiliappan
knotserver: git: add more fields to NiceDiff.Commit
1y ago
ea1b3729
service
knotserver: git/service: refactor execution of git service command
1 year ago
diff.go
knotserver: git: add more fields to NiceDiff.Commit These should now let us reconstruct the commit object (or at least the git cat-file equivalent) appview-side. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>
1 year ago
fork.go
knotserver: fork: add function to sync fork
1 year ago
git.go
knotserver: git: improve performance of last_commit_time uses `git log --name-only` to speed things along. the performance tradeoff here is that active repositories tend to load last-commit times really quickly, but directories with one file that was modified 20k commits ago will result in the entire log being walked through. git-log command is parsed as it streams to avoid having to wait for the entire command to complete, and as soon as the entire directory's listing is hydrated, we cancel the command. most of the time, this results in hydration of subdirectories also (this gets cached), resulting in good experience when browsing a repo (typically moving down directories gets faster with each click, as fewer files need hydration). Signed-off-by: oppiliappan <me@oppi.li>
1 year ago
last_commit.go
knotserver: git: improve performance of last_commit_time uses `git log --name-only` to speed things along. the performance tradeoff here is that active repositories tend to load last-commit times really quickly, but directories with one file that was modified 20k commits ago will result in the entire log being walked through. git-log command is parsed as it streams to avoid having to wait for the entire command to complete, and as soon as the entire directory's listing is hydrated, we cancel the command. most of the time, this results in hydration of subdirectories also (this gets cached), resulting in good experience when browsing a repo (typically moving down directories gets faster with each click, as fewer files need hydration). Signed-off-by: oppiliappan <me@oppi.li>
1 year ago
merge.go
knotserver: merge using git-am if format-patch is detected
1 year ago
repo.go
set default branch from KNOT_REPO_MAIN_BRANCH
1 year ago
tree.go
knotserver: git: improve performance of last_commit_time uses `git log --name-only` to speed things along. the performance tradeoff here is that active repositories tend to load last-commit times really quickly, but directories with one file that was modified 20k commits ago will result in the entire log being walked through. git-log command is parsed as it streams to avoid having to wait for the entire command to complete, and as soon as the entire directory's listing is hydrated, we cancel the command. most of the time, this results in hydration of subdirectories also (this gets cached), resulting in good experience when browsing a repo (typically moving down directories gets faster with each click, as fewer files need hydration). Signed-off-by: oppiliappan <me@oppi.li>
1 year ago