| commit | bc381a412096255db1253d0df890e2bddc19ea37 | [log] [download] |
|---|---|---|
| author | Shawn Pearce <sop@google.com> | Mon Jun 22 12:17:43 2015 -0700 |
| committer | Shawn Pearce <sop@google.com> | Mon Jun 22 17:09:45 2015 -0700 |
| tree | beb95f80faa172e92b923973cab73e77a54878d8 | |
| parent | 25d919614e30d86f85f779aee30100ac8210904d [diff] |
Markdown: optionally ping Google Analytics If google.analyticsId is defined in gitiles.config the Google Universal Analytics Web Tracking code will be automatically inserted into the footer of the page with the specified property ID. This will trigger an async load of the tracking code, and an async ping of the page visit. Change-Id: I0adb1e3f8291f8fcab3bff8eb1847b215c103a9a
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
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.
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.
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