commit | c10cc990c91c67ee834840e64f359d9103c06630 | [log] [tgz] |
---|---|---|
author | Shawn Pearce <sop@google.com> | Mon Feb 09 00:22:33 2015 -0800 |
committer | Shawn Pearce <sop@google.com> | Tue Jun 23 15:04:25 2015 -0700 |
tree | 00ae19f5214561693eb403a50762d526231e8378 | |
parent | bc381a412096255db1253d0df890e2bddc19ea37 [diff] |
Markdown: apply prettify to verbatim blocks Verbatim blocks may optionally specify a language, e.g.: ```java import java.io.InputStream; ``` If the named language is known to be supported by prettify parser try to format with syntax highlighting and include that styled result in the HTML. Avoid recreating the Prettify instance each time a block needs to be formatted. Prettify can be run over multiple inputs but is not thread-safe due to updates of the file extension map while loading a language that has not been processed before. Replacing the map with a synchronized map during init will prevent internal map corruption when concurrent threads initialize languages. Change-Id: Ia37628d7c440df0170a21e69383ab69b20e85beb
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