From: "Laszlo Ersek" <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Tianocore-docs Gitbook offline document status (PDF, EPUB, MOBI)
Date: Tue, 20 Oct 2020 10:43:56 +0200 [thread overview]
Message-ID: <978d0d25-85de-cb21-b0b0-2189ec60bc7e@redhat.com> (raw)
In-Reply-To: <MN2PR11MB44619CB0EB0407554B94CFF4D21F0@MN2PR11MB4461.namprd11.prod.outlook.com>
On 10/20/20 02:26, Kinney, Michael D wrote:
> One feature I forgot to mention with this approach is that a developer fork of
> a tianocore-docs repo with this Gitbook action enabled provides the developer
> the option of enabling the Gitbook action on their fork. This allows doc edits
> to be performed on the developer fork and published versions of the documents
> are generated in the gh-pages branch of that fork when a push is made to the
> master or release/* branches. Other branches can be created to work on edits
> and on demand GitHub action feature called workflow_dispatch is enabled that
> allows the GitHub action to be run on a branch selected from a dropdown.
> You can see this drop down called "Run workflow" in the following page:
>
> https://github.com/tianocore-docs/edk2-TemplateSpecification/actions?query=workflow%3A%22Gitbook+Action+Build%22
>
> This removes the need for developers to locally install the Gitbook CLI tools
> to verify the published document output.
Great!
I'm sure I'll forget the details very soon, but I think I'll remember
that doing this is *possible*, so I'll either find your guidance in my
mailbox, or just ask you again. :)
Thanks!
Laszlo
next prev parent reply other threads:[~2020-10-20 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 3:48 Tianocore-docs Gitbook offline document status (PDF, EPUB, MOBI) Michael D Kinney
2020-10-19 18:59 ` [edk2-devel] " Laszlo Ersek
2020-10-19 20:33 ` Michael D Kinney
2020-10-20 0:26 ` Michael D Kinney
2020-10-20 8:43 ` Laszlo Ersek [this message]
2020-10-20 8:42 ` Laszlo Ersek
2020-10-26 18:57 ` Michael D Kinney
2020-10-26 19:19 ` Kirkendall, Garrett
2020-10-26 19:23 ` Michael D Kinney
2020-11-13 22:39 ` Laszlo Ersek
2020-11-30 19:16 ` Shaw, Kevin W
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=978d0d25-85de-cb21-b0b0-2189ec60bc7e@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