| commit | 10e68e650044f7b749a5ccbe9c4032b7950f5835 | [log] [tgz] |
|---|---|---|
| author | Shawn Pearce <sop@google.com> | Sat Jan 02 09:37:58 2016 -0800 |
| committer | Shawn Pearce <sop@google.com> | Tue Jan 05 10:42:34 2016 -0800 |
| tree | fee86d5d6ac9810f6d6b0612115d423e53c08dee | |
| parent | 83c28f02f4039f60a0b01ed159fa3a255b4018f9 [diff] |
Make HEAD cheaper for RepositoryIndex On HEAD requests avoid doing any log processing or content generation and just issue back 200 OK. This allows clients to use HEAD to probe for existance of a repository and get back 200 OK from the servlet or 404 Not Found from the higher level resolving filter. Provide the same in HostIndexServlet to look for subdirectories of repositories. If there are no repositories with that prefix return 404 Not Found. Change-Id: Ie69a7da327f1c01a214ca8608580b51577ad9ce2
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