Gitiles v0.1-7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJWeX8tAAoJEF/XxZqaEoiMcD8P/A7cbYAdqJXXAXsK+chpByXY
Qh4SyPLvZg2YViOYPStXFag6VDV1yq6PYv0B8kzTeg6lHvK0XGhW1pfUpIRnoS/i
Y3PHBr6qQhkAqv89N5WLl4tLT0tL3Mq4Pbfr33n0dD7cXhc8qWsbQjomIyGp+Sw2
x7+TZhCptKVCQJNA47tUzod6eubkop845vg4JYVxxnyeLoPxmaJt+ble7bEXU0qp
qsJLGUiI/S4/oOmNTEW9jzIHJCCX+o9T5qSGoOiPSaOAUH8RtjGukVoDhe9Hi4I7
dK+Bn+617wxau78GTU6jeIbVXEDUqiz6xBIY4GeEsXS6xZBKkMBYq4rvgN6a+FOm
6q7Z8MHn1xo1vrSb/GkJ368rJZV7I+5F+JXnxVcXHdiH2QwOoft1s3luWQZiRZRm
Ke0jpv1Cx/l5Me8pHxlvw9iISLN+d2RD1IGhJgVcyY7ib64q8NXowLSwAgmPqUus
T0K0vgnDZcDbgebPcclQV7H7oSs78cc5CE0N1pDnq5f+755AUJhPEaTmJbVhOv4n
anSG2l75DFiT7fWr+pnQeNW0frAKdyTdQ29s1doTxQ6DoLGwXsah4D6u6l10Ys+t
1hms61D5e+eWXygbnBQrnTPPbfp1tFpRjsphnbhbp+jShntKaV5LVTupScCLSl8I
OD2NHaEzP86ho2+ebkcd
=KJwQ
-----END PGP SIGNATURE-----
Bump version to 0.1-7

Change-Id: I871d4c6828a8881e64567b6e4f7c5b0772de4c3d
1 file changed
tree: 0d0a5c8f71e9de7141575a70e6ba95e4f980b606
  1. .buckconfig
  2. .gitignore
  3. .gitmodules
  4. .settings/
  5. BUCK
  6. COPYING
  7. Documentation/
  8. README.md
  9. VERSION
  10. bucklets.defs
  11. fake_pom_deploy.xml
  12. gitiles-dev/
  13. gitiles-servlet/
  14. gitiles-war/
  15. lib/
  16. tools/
README.md

Gitiles - A simple JGit repository browser

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.

Building

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

Testing

  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.

Eclipse IDE

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.

Code Style

Java code in Gitiles follows the [Google Java Style Guide] (https://google.github.io/styleguide/javaguide.html) with a 100-column limit.

CSS in Gitiles follows the [SUIT CSS naming conventions] (https://github.com/suitcss/suit/blob/master/doc/naming-conventions.md).

Code Review

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