| commit | b33426e831fca57fc93d9f8a6751c5d9aa82aeea | [log] [download] |
|---|---|---|
| author | Andrew Bonventre <andybons@chromium.org> | Wed Sep 09 18:28:28 2015 -0400 |
| committer | Andrew Bonventre <andybons@chromium.org> | Wed Sep 16 13:42:56 2015 -0400 |
| tree | 7005db09e24cfece8d6eda0f99a5d2fedd06000c | |
| parent | 9be60227c5caf4eb767ac868aeab33d10904d365 [diff] |
[CSS] Overhaul of CSS and UX clean up. + CSS is written using the SUITCSS conventions outlined here: https://github.com/suitcss/suit/tree/master/doc + Moved from XHTML -> HTML5. + New flexbox-based layout for all pages. + General cleanup of styles and UI. These changes are to increase readability, reduce clutter in the UI, and establish a visual hierarchy that's persistent across pages. High contrast and larger font sizes are favored. + Some random FE cleanup within the soy and servlets. Change-Id: I2af6c140e82d34d12191bafb5b01f60926370b0b
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