Merge pull request #3 from TrustedComputingGroup/test-pr

Re-do actions, update pandoc

.github/workflows/actions.yml

@@ -0,0 +1,44 @@
+# Render the spec to PDF and Word on pull requests and releases, attaching the
+# outputs to the pull request / release, as appropriate.
+
+name: Render spec
+
+on:
+ pull_request:
+ release:
+ types: [published]
+
+jobs:
+ render:
+ runs-on: ubuntu-latest
+ container:
+ image: ghcr.io/trustedcomputinggroup/pandoc:0.8.1
+ name: Render PDF
+ steps:
+ - name: Checkout
+ uses: actions/checkout@v3
+
+ - name: Render
+ uses: trustedcomputinggroup/[email protected]
+ with:
+ extra-build-options: "--gitstatus --plain_quotes"
+ input-md: spec.md
+ output-pdf: spec.pdf
+ output-docx: spec.docx
+
+ - name: Upload PDF to PR
+ uses: actions/upload-artifact@master
+ if: ${{ github.event_name == 'pull_request' }}
+ with:
+ name: spec
+ path: spec.pdf
+
+ - name: Upload PDF and docx to release
+ uses: svenstaro/upload-release-action@v2
+ if: ${{ github.event_name == 'release' }}
+ with:
+ repo_token: ${{ secrets.GITHUB_TOKEN }}
+ file: spec.*
+ tag: ${{ github.ref }}
+ overwrite: true
+ file_glob: true

main.md → spec.md

@@ -1,10 +1,6 @@
 ---
 title: "Document Title"
-version: 0.1
-revision: 1
-date: 2022/09/17
 type: SPECIFICATION
-status: DRAFT
 ...
 
 ---
@@ -43,11 +39,11 @@ owners.
 
 # Change History
 
-| **Revision** | **Date** | **Description** |
-| ------------ | ---------- | --------------- |
-| 0.1/1 | 2022/09/17 | Initial draft |
-
----
+--------------------------------------------------------------------------------
+**Version** **Date** **Description**
+----------- ---------- ---------------------------------------------------------
+0.1 2024/01/29 Initial draft
+--------------------------------------------------------------------------------
 
 # Document Style
 
@@ -72,6 +68,7 @@ comment_, it can be considered a _normative statement_.
 
 EXAMPLE:
 
+::: Informative :::
 > This is the first paragraph of 1–n paragraphs containing text of the kind
 > informative comment ...
 >
@@ -81,6 +78,7 @@ EXAMPLE:
 >
 > To understand the TCG specification, the user must read the specification.
 > (This use of MUST does not require any action).
+:::::::::::::::::::
 
 ---