commit | d57ade0da21f09f579833c34152037976b55a189 | [log] [tgz] |
---|---|---|
author | Shawn Pearce <sop@google.com> | Mon Jun 22 12:34:38 2015 -0700 |
committer | Shawn Pearce <sop@google.com> | Mon Jun 22 16:34:11 2015 -0700 |
tree | a77eb00a5746fa95ba957b231b1d7952ee8c843b | |
parent | 6ec5b2e9383eec2edc1a4420ed53a1aed9126989 [diff] |
Markdown: table of contents with duplicate section titles If a document uses the same subsection title underneath multiple sections (e.g. an H3 section "Examples" repeated under each H2 section) gracefully support this by prefixing the id with the titles of the parent sections. If this is still insufficient to get unique id anchors number them using -1, -2, -3, etc. suffixes based on order within the document. Bug: issue 75 Change-Id: I6cfa92b0b3ae881a7e4e46f9440dcaaa0b0bb7f3
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