|author||David Ostrovsky <firstname.lastname@example.org>||Tue Aug 29 08:08:16 2017 +0200|
|committer||David Ostrovsky <email@example.com>||Tue Aug 29 07:20:20 2017 +0000|
Stamp final artifacts Merge Implementation-Version into the final artifacts. This has two advantages: for one, it can be later tracked down, from what release this artifact was consumed; for another, in case a release was produced without touching any source files but only bumping some dependencies, that are not shaded in the final artifacts and thus do not contribute to the SHA1 update of the final artifacts, the SHA1 would still change, because of the changed content of the META-INF/MANIFEST.MF file. For example building from this commit will produce the following manifest content: $ bazel build java/com/google/gitiles/blame/cache:cache-stamped bazel-genfiles/java/com/google/gitiles/blame/cache/cache-stamped.jar Unzipping the content of the cache-stamped.jar produces the following implementation version: $ cat META-INF/MANIFEST.MF | grep -i Impl Implementation-Version: v0.2-3-7-g9af1a70 Change-Id: Idb6e7c635ae254188e1ee6592e0e0502c7c338a6
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.