From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: TianoCore-docs GitBook Documentation Process
Date: Tue, 11 Jul 2017 19:05:13 +0200 [thread overview]
Message-ID: <48511335-6c66-b536-8685-4f14bbc010e8@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7D5951F@ORSMSX113.amr.corp.intel.com>
On 07/11/17 17:21, Kinney, Michael D wrote:
> Laszlo,
>
> I found a GitBook plugin that can provide the branch name and
> the SHA hash in either short or long form.
>
> https://plugins.gitbook.com/plugin/gitversion
>
> Here is an example patch to the EDK II Template Specification
> That add this plugin to book.json and add the branch name and
> SHA hash below the build time/date stamp of the document.
>
> diff --git a/README.md b/README.md
> index 30edb2a..4ad8a96 100644
> --- a/README.md
> +++ b/README.md
> @@ -41,6 +41,10 @@
>
> ** {{ gitbook.time|date('MM/DD/YYYY hh:mm:ss') }} **
>
> +** {{ "GIT branch: " | gitBranch }} **
> +
> +** {{ "GIT hash: " | gitLong }} **
> +
> {% if book.udkrelease %}
> ** {{ book.udkrelease }} **
> {% endif %}
> diff --git a/book.json b/book.json
> index 8c58ffe..d94cbcc 100644
> --- a/book.json
> +++ b/book.json
> @@ -5,6 +5,6 @@
> "version" : "Revision 0.20"
> },
>
> - "plugins": ["puml"],
> + "plugins": ["puml", "gitversion"],
> "pluginsConfig": {}
> }
Ah, great!
Does the fact that the plugin list is provided in the book itself (in
"book.json") imply that gitbook.com too will load the plugin, and
generate the right output, in these "remote" renderings?
Thank you,
Laszlo
next prev parent reply other threads:[~2017-07-11 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:37 TianoCore-docs GitBook Documentation Process Kinney, Michael D
2017-07-08 21:35 ` Laszlo Ersek
2017-07-10 16:43 ` Kinney, Michael D
2017-07-10 20:38 ` Laszlo Ersek
2017-07-11 15:21 ` Kinney, Michael D
2017-07-11 17:05 ` Laszlo Ersek [this message]
2017-07-11 17:15 ` Kinney, Michael D
2017-07-12 18:12 ` Kinney, Michael D
2017-08-11 16:30 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48511335-6c66-b536-8685-4f14bbc010e8@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox