commit | b7e872dd7ec83d4dd17aa0371807bde25abfc63f | [log] [tgz] |
---|---|---|
author | Shawn Pearce <sop@google.com> | Fri Jul 10 15:21:47 2015 -0700 |
committer | Shawn Pearce <sop@google.com> | Fri Jul 10 16:47:37 2015 -0700 |
tree | 415141baed1254293ea743066e7cb4f380d984c6 | |
parent | d4d031d7daee64873cf0497e032ad3a4907a8c45 [diff] |
Fix relative and absolute markdown links within repo [link](/a) should resolve relative to the top of the repository, not the top of the host. [link](../../C) from within A/B/ should correctly resolve to /C and not a broken link. Update DocServletTest to fix tests previously broken by anchor hyperlink widgets (263d674ee88311b3b). Change-Id: I036c47f22a52d82919f7472c751db766b88d23f7
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