| commit | 2eb75f0da734d8eeb655e10db99b98976dd72e28 | [log] [download] |
|---|---|---|
| author | David Pursehouse <dpursehouse@collab.net> | Sat Feb 15 11:40:37 2020 +0900 |
| committer | David Pursehouse <dpursehouse@collab.net> | Sat Feb 15 11:40:37 2020 +0900 |
| tree | 546fbfa61a8f9fabf383e0547401440503c7a49f | |
| parent | 314611cc6d5e62bcf00ce5b66ab82d084de65c06 [diff] | |
| parent | a373f641be2ecc9209feeef38edb6989bc9948bb [diff] |
Merge branch 'stable-0.2'
* stable-0.2:
Bump version to 0.2-12
Bump required Bazel version to 2.1.0
Upgrade bazlets to latest master revision
Set version to 0.2-7.1
Fix formatting of Soy files
Bump bazel version to 1.2.0
Backport all build-related commits from master to stable-0.2
Enable more error-prone checks
Enable error-prone checks by default
Update bazel options to align with gerrit's
tools/eclipse/project.sh: Use bazel query to find project.py
Harmonize build rule names to use hyphen instead of underscore
Check BLOB content size before trying to render it
BlameCacheImpl: Avoid NPE if path does not exist
Navbar: Fix handling of [home] and [logo] metalinks
Don't render navbar.md metadata in html
Format with google-java-format 1.7
Do not retain body in RevisionParser walk
Remove unnecessary parseBody call from LogServlet
Ensure RevTag is parsed before using its body
Ensure RevCommit is parsed before using its content
Require a RevWalk when building CommitData
Convert /** @param */ to {@param} in Soy.
RefServlet: Use full refname in link
Automatically format all build files with buildifier lint mode
Change-Id: Ib9b31c72c276c6f95cd78802ffe818fb52338b68
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 automatically renders *.md Markdown files into HTML for simplified documentation. Refer to the Markdown documentation for details.
Gitiles is configurable in a git-style configuration file named gitiles.config. Refer to the configuration documentation for details.
Use the issue tracker at github to file bugs.
Please refer to the Developer Guide.