core/knotserver/git/ at ec58ee88eac344a9c3f7f4048dd3063d9385e218 · alice.pds.demo.boltless.dev/core · Tangled

alice.pds.demo.boltless.dev / core

0

This repository has no description

0

core / knotserver / git

1 folder 8 files

at ec58ee88eac344a9c3f7f4048dd3063d9385e218

Anirudh Oppiliappan cmd,knotserver: clean up 1y ago

knotserver: git/service: refactor execution of git service command

1 year ago

cmd,knotserver: clean up Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

1 year ago

knotserver: fork: add function to sync fork

1 year ago

cmd,knotserver: clean up Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

1 year ago

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

knotserver: git: cache merge check results Signed-off-by: oppiliappan <me@oppi.li>

1 year ago

post_receive.go

knotserver: include committer metadata for each ref update Signed-off-by: oppiliappan <me@oppi.li>

1 year ago

set default branch from KNOT_REPO_MAIN_BRANCH

1 year ago

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