commit | 576d7b62a9346cc8e020a518e1c31c2ac64f464d | [log] [tgz] |
---|---|---|
author | Shawn Pearce <sop@google.com> | Mon Mar 30 09:16:19 2015 -0700 |
committer | Shawn Pearce <sop@google.com> | Mon Mar 30 09:16:19 2015 -0700 |
tree | 0a7d608973234d671dd1d511b8200cfdc76f3560 | |
parent | cb2850184f5dee5eb7039c3c42f44bd906347ec5 [diff] |
Markdown: Redirect to show source file if parsing fails If the file cannot be parsed as markdown redirect the browser to view the source of the file. This will at least permit the end user to read the raw contents, instead of getting a 500 error with no links forward. Change-Id: I124349dbe1fedb9203699653b802f19ad58f4baa
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