AgeCommit message (Collapse)AuthorLines
Share the rename fixture of the diff pagesBryce Kwon-9/+1
Each repository is built tree for tree as before. A helper that lost the caller's change would still fail t0107, where following no path shows file-1, but t0108 passed without its added line, so it now looks for that line.
Compare more of the patch page with gitBryce Kwon-33/+82
The root patch was checked for its signature alone, so one that lost its diff passed. The headers, the note a path adds to the stat and a merge in a range had no test, and a renamed file's patch was grepped rather than compared. The version is read in the test that needs it, so a missing build/VERSION fails there instead of surfacing later as a mismatch.
Check which commits max-patch-count keepsBryce Kwon-9/+21
Only the number of patches was counted, so keeping the oldest two of a range would have passed. The default of 50 and the 0 that lifts the bound had no test.
Test enable-plain-email=0 where it changes outputBryce Kwon-0/+10
No test set it, though it switches the patch to a format of cgit's own and drops the address from the feed and the trailer idents.
Show a renamed file's diff as the renameBryce Kwon-0/+19
A diff limited to the new name cannot see the old one, so the diffstat's link for a renamed file, the commit page reached from that file's log, and the file's rawdiff and patch all showed every line as added. A path the old tree lacks is now diffed across the whole commit with rename detection aimed at it alone, the way git blame looks for a rename, so it is compared with the commit's deleted files and nothing else. Doing it in cgit_diff_tree keeps the log's counts for that commit in step with the page they link to. The rawdiff and patch pages leave the diff to git's own output, so for them that search finds the old name, and both names go into the limit with rename detection on.
Write the remaining config copies with cgitrc_copyBryce Kwon-4/+1
Write the diff and patch checks as the suite doesBryce Kwon-11/+11
Ask for a url through cgit_url everywhereBryce Kwon-3/+3
Add the shared config writers and cgit_rcBryce Kwon-2/+2
The helpers are named by kind. cgitrc_repo and cgitrc_copy write the config file named first, and cgit_url, cgit_query and cgit_rc run cgit, each named after what it is handed first. A repository copies its defaults from the globals read before its repo.url, so cgitrc_repo places every setting itself, and a global can no longer land where it silently stops applying. The t00xx and t01xx files move to them here.
Correct the test comments that went staleBryce Kwon-2/+1
Reuse the ids t0109 has already looked upBryce Kwon-2/+0
Drop the patch greps the comparisons already makeBryce Kwon-20/+0
The From, Date, Subject and signature lines are part of what the next test compares in full against git format-patch, for the single commit and for the range alike.
Offer the versions as an optionBryce Kwon-4/+14
enable-version-info brings back the cgit and git versions that 872bd7c took off the footer and the generator tag, for a site that wants them, and the version f7d2b83 put on the signature of patches now follows it too. It stays off by default for the reason 872bd7c gave.
Sign patches with the cgit versionBryce Kwon-3/+7
git format-patch ends each patch with the version of git that wrote it, and the bare "cgit" that 872bd7c left in its place said less. The version is written as git writes its own, without the v of the tag, so a release build signs with "cgit 2.9.0". The footer and the generator tag still leave versions out.
Keep the version numbers off the pagesBryce Kwon-6/+3
The generator meta, the footer and the patch signature named the exact cgit and git versions on every response, which only helps someone matching a site against an advisory. The shipped server configs already hide the server's own version for the same reason, and cgit --version still answers on the host.
Clean up the whole treeBryce Kwon-10/+5
Trim the comments and dead code across the treeBryce Kwon-19/+30
Collect test output under trash and resultsBryce Kwon-2/+2
Renumber the test scripts into themed rangesBryce Kwon-0/+0
The numbering walks outward from the ground the suite stands on. - t000x for the git version, html validity and the cache - t01xx for page content, one script per page - t02xx for filters, submodule links, dates and limits, which cut across pages - t03xx for defence, the security regressions and the $HOME promise - t04xx for the helper tools under tools/
Tidy the test comments and shell portabilityBryce Kwon-0/+7
Add max-patch-count to bound the patch viewBryce Kwon-0/+13
Reorganise into source, assets and librariesBryce Kwon-2/+2
Everything the build generates now lands in build/, so a clean is a single remove and the source tree stays free of build output.
ui-patch: match git-format-patch(1) outputJohn Keeping-2/+2
Using (DIFF_FORMAT_DIFFSTAT | DIFF_FORMAT_PATCH) causes Git to emit a "---" line between the commit message and the body of the patch, which fixes a regression introduced in commit 455b598 (ui-patch.c: Use log_tree_commit() to generate diffs, 2013-08-20), prior to which we inserted the "---" line ourselves. DIFF_FORMAT_SUMMARY is added so that we match the output of git-format-patch(1) without the "-p" option. Signed-off-by: John Keeping <john@keeping.me.uk>
t0108: modernize styleJohn Keeping-10/+10
* &&-chaining * use test_cmp instead of cmp * use strip_headers instead of knowing how many lines there will be Signed-off-by: John Keeping <john@keeping.me.uk>
t0108: Add tests for revision rangesLukas Fleischer-0/+17
Add tests to check whether generating multiple patches at once works. Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
t0108: Compare output with git-format-patch(1)Lukas Fleischer-0/+7
Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
ui-patch.c: Add additional newline after each patchLukas Fleischer-2/+2
For consistency with git-format-patch(1). Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
t0108: Avoid unnecessary fork()Lukas Fleischer-1/+1
Use `git rev-list --max-parents=0 HEAD` instead of `git rev-list HEAD | tail -1` to get the root commit. This works since Git 1.7.4.2. Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
tests: use Git's test frameworkJohn Keeping-19/+18
This allows tests to run in parallel as well as letting us use "prove" or another TAP harness to run the tests. Git's test framework requires Git to be fully built before letting any tests run, so add a new target to the top-level Makefile which builds all of Git instead of just libgit.a and make the "test" target depend on that. Signed-off-by: John Keeping <john@keeping.me.uk>
tests: make whitespace consistentJohn Keeping-1/+1
Signed-off-by: John Keeping <john@keeping.me.uk>
tests: "grep -e" is not portable to all platformsJohn Keeping-5/+5
The "-e" option to grep is not needed unless specifying more than one pattern, which we don't do. Remove it to avoid restricting the tests on platforms that do not have a grep that recognises "-e". Signed-off-by: John Keeping <john@keeping.me.uk>
tests: handle paths with whitespaceFerry Huberts-1/+1
v2: incorporate remarks of Lukas Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
t0108-patch: add 'tests_done' to endMark Lodato-0/+2
Signed-off-by: Mark Lodato <lodatom@gmail.com>
Fix segfault in patch view for root commitLars Hjemli-0/+37
The code for patch view assumed the current commit would always have a parent, which made cgit segfault when that wasn't the case. This fixes the bug and adds a test-script for patch view which includes a test for the inital commit. Signed-off-by: Lars Hjemli <hjemli@gmail.com>
Copyright © 2026 Bryce Kwon. All Rights Deprecated.