All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: virtio-comment@lists.linux.dev
Subject: Re: [PATCH v2 10/10] .github: add a runner to build the latest draft
Date: Fri, 10 Oct 2025 10:06:45 -0400	[thread overview]
Message-ID: <20251010100110-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87zf9yvowy.fsf@draig.linaro.org>

On Fri, Oct 10, 2025 at 02:58:53PM +0100, Alex Bennée wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
> 
> > On Fri, Oct 10, 2025 at 12:20:10PM +0100, Alex Bennée wrote:
> >> This will run each time anything is pushed to the repository and store
> >> the result in the release assets area of github. To see an example of
> >> it in practice see the virtio-msg repo:
> >> 
> >>   https://github.com/Linaro/virtio-msg-spec/releases
> >
> > Is this the PDF?
> >
> > https://github.com/Linaro/virtio-msg-spec/releases/download/virtio-msg-rfc1-Linaro-draft-v14/virtio-msg-rfc1-Linaro-draft-v14.pdf
> >
> >
> > Some comments:
> > I suggest removing the version (e.g. replace with X.X)
> 
> Isn't the closest version still useful (to know its not based on a
> really old version of the spec)?

Not sure. E.g. in this case this is *before* 1.4 and later one
will maybe be *after* 1.4, and not sure we'll remember to update.
Just worried people will get confused. Not critical I guess...
Maybe stick something else in there to make it clear?  X.1.4 ?

> > Replacing "Working Draft" with just "Draft"
> > Maye stick the hash there too?
> 
> I've gone with:
> 
>   Unofficial Draft (@ git 8c7a1c3 with local changes)
> 
> to make it clear its outside of the normal OASIS stats.

Sounds good. Maybe "ud" in the file name then like we did
for wd?

> > I also see front page corruption:
> > driver listing overlaps with related work.
> 
> I think that predates my changes - I built from current HEAD and it has
> the some overlap.

No, it's another problem with the toolchain used - I built it on latest
fedora and it does not have this issue.

> For the unofficial draft should we just elide the stage information
> entirely as the links it generates don't point anywhere?

I wouldn't bother too much and after all the point is to
speed up development so it's useful to make it look
close to what the official one will look like.

> >
> >
> >
> >
> >
> >
> >> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> >> Message-ID: <20251008145916.2626143-10-alex.bennee@linaro.org>
> >> ---
> >>  .github/workflows/deploy.yaml | 37 +++++++++++++++++++++++++++++++++++
> >>  .github/workflows/test.yml    | 15 ++++++++++++++
> >>  2 files changed, 52 insertions(+)
> >>  create mode 100644 .github/workflows/deploy.yaml
> >>  create mode 100644 .github/workflows/test.yml
> >> 
> >> diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml
> >> new file mode 100644
> >> index 0000000..fec4910
> >> --- /dev/null
> >> +++ b/.github/workflows/deploy.yaml
> >> @@ -0,0 +1,37 @@
> >> +name: Deploy current state
> >> +
> >> +on: [push]
> >> +
> >> +jobs:
> >> +  build:
> >> +    runs-on: ubuntu-latest
> >> +    steps:
> >> +      - uses: actions/checkout@v4
> >> +      - uses: xu-cheng/texlive-action@v2
> >> +        with:
> >> +          scheme: full
> >> +          run: |
> >> +            apk add file font-liberation make zip
> >> +            make local-all
> >> +            echo ${{ github.sha }} > Release.txt
> >> +
> >> +      - name: Create Draft Release
> >> +        id: create_release
> >> +        uses: actions/create-release@v1
> >> +        env:
> >> +          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
> >> +        with:
> >> +          tag_name: ${{github.ref_name}}-${{ github.repository_owner }}-draft-v${{ github.run_number }}
> >> +          release_name: Draft ${{ github.run_number }}
> >> +          draft: false
> >> +          prerelease: false
> >> +
> >> +      - name: Upload Release Asset
> >> +        uses: actions/upload-release-asset@v1
> >> +        env:
> >> +          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
> >> +        with:
> >> +          upload_url: ${{ steps.create_release.outputs.upload_url }}
> >> +          asset_path: virtio-v1.4-wd01.pdf
> >> +          asset_name: ${{github.ref_name}}-${{ github.repository_owner }}-draft-v${{ github.run_number }}.pdf
> >> +          asset_content_type: application/pdf
> >> diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
> >> new file mode 100644
> >> index 0000000..34f4f44
> >> --- /dev/null
> >> +++ b/.github/workflows/test.yml
> >> @@ -0,0 +1,15 @@
> >> +name: CI
> >> +
> >> +on: [pull_request]
> >> +
> >> +jobs:
> >> +  build:
> >> +    runs-on: ubuntu-latest
> >> +    steps:
> >> +      - uses: actions/checkout@v4
> >> +      - uses: xu-cheng/texlive-action@v2
> >> +        with:
> >> +          scheme: full
> >> +          run: |
> >> +            apk add file make zip
> >> +            make local-html
> >> -- 
> >> 2.47.3
> >> 
> 
> -- 
> Alex Bennée
> Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-10-10 14:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 11:20 [PATCH v2 00/10] QoL tweaks and github action Alex Bennée
2025-10-10 11:20 ` [PATCH v2 01/10] LICENSE.md: convert html to proper MarkDown Alex Bennée
2025-10-30  7:10   ` Manos Pitsidianakis
2025-10-10 11:20 ` [PATCH v2 02/10] README.md: convert embedded " Alex Bennée
2025-10-10 11:20 ` [PATCH v2 03/10] REVISION: update to 1.4-wd01 Alex Bennée
2025-10-10 11:20 ` [PATCH v2 04/10] .gitpublish: update base to current working branch Alex Bennée
2025-10-10 11:20 ` [PATCH v2 05/10] virtio-html.tex: sort package list Alex Bennée
2025-10-10 11:20 ` [PATCH v2 06/10] specvars.tex: properly wrap arguments to \urldef Alex Bennée
2025-10-10 11:53   ` Michael S. Tsirkin
2025-10-10 13:49     ` Alex Bennée
2025-10-10 11:20 ` [PATCH v2 07/10] virtio-html.cfg: implement workaround for htlatex regression Alex Bennée
2025-10-10 11:20 ` [PATCH v2 08/10] make-setup-generated: optionally add GIT metadata Alex Bennée
2025-10-10 11:52   ` Michael S. Tsirkin
2025-10-10 13:10     ` Alex Bennée
2025-10-10 13:16       ` Michael S. Tsirkin
2025-10-10 13:48         ` Alex Bennée
2025-10-10 11:20 ` [PATCH v2 09/10] Makefile: add some simple make automations Alex Bennée
2025-10-10 11:20 ` [PATCH v2 10/10] .github: add a runner to build the latest draft Alex Bennée
2025-10-10 12:00   ` Michael S. Tsirkin
2025-10-10 13:58     ` Alex Bennée
2025-10-10 14:06       ` Michael S. Tsirkin [this message]
2025-10-10 12:06 ` [PATCH v2 00/10] QoL tweaks and github action Michael S. Tsirkin

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-all 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=20251010100110-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=virtio-comment@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.