commit | bc0eaaafbcd32668b088b79303b2079f0f21ea15 | [log] [tgz] |
---|---|---|
author | Björn Pedersen <bjoern.pedersen@frm2.tum.de> | Tue Mar 29 15:30:29 2016 +0200 |
committer | Björn Pedersen <bjoern.pedersen@frm2.tum.de> | Tue May 31 13:40:44 2016 +0200 |
tree | 891529d0687bedc798b63029c225ef2fb813b61a | |
parent | ed3c2d11fc470e317df9c9fc9f61cba64f77a221 [diff] |
Improve styling/branding options In addition to the header introduce more customizable template parts that are depending on 'customVariant' to make injection of HTML at various places possible. The 'customHeader' config variable is renamed to 'customVariant', but the old name is still recognised as an alias for the new name to ensure backwards compatibility. The new template parts are: customHeadTagPart -> at the end of the <head> tag customFooter -> The footer tag with contents The new fixed templates .footerFormatBadge and .footerPoweredBy can be used in custom footers. Change-Id: I95a97a3805f4fb3011bc932d4f9799ec5a2c78c4
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 buck test
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
.
To run unit tests, run buck test
.
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.
Java code in Gitiles follows the Google Java Style Guide with a 100-column limit.
Code should be automatically formatted using google-java-format prior to sending a code review. There is currently no Eclipse formatter, but the tool can be run from the command line:
java -jar /path/to/google-java-format-1.0-all-deps.jar -i path/to/java/File.java
CSS in Gitiles follows the SUIT CSS naming conventions.
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