| commit | 978fe8e37481e83c145c152729d94bf4dcc56296 | [log] [download] |
|---|---|---|
| author | Shawn Pearce <sop@google.com> | Wed Mar 25 16:49:41 2015 -0700 |
| committer | Shawn Pearce <sop@google.com> | Wed Mar 25 16:54:27 2015 -0700 |
| tree | d985d0cc299d52ae268fe0c2330c4fa0e8440823 | |
| parent | 3d41659932966891b0e934ce6895059c26be9fcf [diff] |
Markdown: Fix relative links in README.md presentation Relative links in a README.md file are rendered inline in a repository index page, a commit, or a tree. Relative links in these files are written relative to the README.md file itself, including its revision, which may not be present current in the GitilesView. Change-Id: Iea72c69336f76ac9bc51c92b9d0308ba950a603e
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