| commit | 1868fce64cce07304b4b031edf1531c8295c8463 | [log] [download] |
|---|---|---|
| author | Shawn Pearce <sop@google.com> | Mon May 11 23:42:32 2015 -0700 |
| committer | Shawn Pearce <sop@google.com> | Mon May 11 23:51:08 2015 -0700 |
| tree | 7681e29ec81c5bcf9593d5d22e5014d381b56c91 | |
| parent | 576d7b62a9346cc8e020a518e1c31c2ac64f464d [diff] |
Clip very long branch names to avoid overflow Repository indexes with huge branch names can see the branch name overlap with recent commit history or README.md file contents. This is caused by the ref list using a "float: left" with a fixed width specification of 200px. Reduce the left side padding to 15px to get more space for the actual branch/tag names while still showing some level of indent below the Branches and Tags headers. Request overflow hidden with ellipsis for truncation in the browser. Expand the lists on the /+refs page to show 500px for each of the Branches and Tags columns, allowing names clipped on the repository index page a better chance to be presented without any clipping after following the "More..." link. Change-Id: I13a833452b7298ac5d45dc63958f8921649cd464
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