From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mx.groups.io with SMTP id smtpd.web09.2640.1603183442359693170 for ; Tue, 20 Oct 2020 01:44:02 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TT0fXtNF; spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1603183441; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=21vElC7u0bpf72SDJIAvAR8Rx1F+Ci8pjSUrj4cOrkw=; b=TT0fXtNFYi3I33yLJhF8hZ/8cqMkr0VrVN8o7c7J3H0ZdXzgmDyTQMXt1ajpPULazEnq8u uXnFgttMd8SvUKiWyFZzz2E2+26JrxEshwSnQ+OMANWCCqELxbcF4vDWPJ5WRGqyHoZRm2 f0WBPHn0Ar12ryHMJRxVaYIqyD0Evr0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-48-DG3a5uKJMKeBpvlHQzW67g-1; Tue, 20 Oct 2020 04:43:58 -0400 X-MC-Unique: DG3a5uKJMKeBpvlHQzW67g-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C299F18C89C2; Tue, 20 Oct 2020 08:43:57 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-240.ams2.redhat.com [10.36.114.240]) by smtp.corp.redhat.com (Postfix) with ESMTP id 368DD55793; Tue, 20 Oct 2020 08:43:57 +0000 (UTC) Subject: Re: [edk2-devel] Tianocore-docs Gitbook offline document status (PDF, EPUB, MOBI) To: "Kinney, Michael D" , "devel@edk2.groups.io" References: <499b75ab-a015-9d5d-f383-780c66338d4d@redhat.com> From: "Laszlo Ersek" Message-ID: <978d0d25-85de-cb21-b0b0-2189ec60bc7e@redhat.com> Date: Tue, 20 Oct 2020 10:43:56 +0200 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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