| commit | cb88d4de3a03fc3ce918949b3cb81005115bcf3c | [log] [tgz] |
|---|---|---|
| author | Dave Borowitz <dborowitz@google.com> | Mon Oct 26 13:58:17 2015 -0400 |
| committer | Dave Borowitz <dborowitz@google.com> | Tue Oct 27 10:16:52 2015 -0400 |
| tree | 1d2b11f48cb1d94f257588f67cbce4e3a04d21b0 | |
| parent | 344c4dd0b3f0ff82caebd8503d00c6df5ac3e5d4 [diff] |
Indicate copy/rename source in HTML log view Eking this out of the RevWalk is a little tricky, because the only way to see when a rename happened is to set a RenameCallback on the FollowFilter. Do this in Paginator, which is already a stateful wrapper around the RevWalk, by keeping track of a map of commit to rename entry present in that commit. Plumb this through to LogSoyData, which is a little ugly because it adds an element after the fact into the entry map produced by CommitSoyData. Actually shoving this all the way through to CommitData would have been more trouble than it's worth. Change-Id: I4538c9a15351f3c1cc5ab1fa7ea7b58e6fa6d4e4
Gitiles is a simple repository browser for Git repositories, built on JGit. Its guiding principle is simplicity: it has no formal access controls, no write access, no fancy Javascript, etc.
Gitiles requires Buck to build.
sudo apt-get install ant
cd ${HOME}
git clone https://github.com/facebook/buck.git
cd buck
ant
sudo ln -s ${PWD}/bin/buck /usr/bin/buck
cd /path/to/gitiles
git submodule update --init
buck build all
buck test
cd /path/to/repositories # Don't run from the gitiles repo. /path/to/gitiles/tools/run_dev.sh
This will recompile and start a development server. Open http://localhost:8080/ to view your local copy of gitiles, which will serve any repositories under /path/to/repositories.
To run unit tests, run buck test.
If you'd like to use Eclipse to edit Gitiles, first generate a project file:
./bucklets/tools/eclipse.py --src
Import the project in Eclipse:
File -> Import -> Existing Projects into Workpace
The project only needs to be rebuilt if the source roots or third-party libraries have changed. For best results, ensure the project is closed in Eclipse before rebuilding.
Java code in Gitiles follows the [Google Java Style Guide] (https://google.github.io/styleguide/javaguide.html) with a 100-column limit.
CSS in Gitiles follows the [SUIT CSS naming conventions] (https://github.com/suitcss/suit/blob/master/doc/naming-conventions.md).
Gitiles uses Gerrit for code review: https://gerrit-review.googlesource.com/
Gitiles uses the “git push” workflow with server https://gerrit.googlesource.com/gitiles. You will need a generated cookie.
Gerrit depends on “Change-Id” annotations in your commit message. If you try to push a commit without one, it will explain how to install the proper git-hook:
curl -Lo `git rev-parse --git-dir`/hooks/commit-msg \
https://gerrit-review.googlesource.com/tools/hooks/commit-msg
chmod +x `git rev-parse --git-dir`/hooks/commit-msg
Before you create your local commit (which you'll push to Gerrit) you will need to set your email to match your Gerrit account:
git config --local --add user.email foo@bar.com
Normally you will create code reviews by pushing for master:
git push origin HEAD:refs/for/master