DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Subject: [PATCH 0/2] GitHub Actions configuration fixes
Date: Wed, 12 Oct 2022 18:29:40 +0200	[thread overview]
Message-ID: <20221012162942.2965188-1-david.marchand@redhat.com> (raw)

GitHub Actions started to deprecated some part of the workflow syntax
and dependencies of some core actions.

This series (mostly) fix those warnings.
For reviewers/testers, this is still moving: I got new warnings while
I was testing the first patch...


-- 
David Marchand

David Marchand (2):
  ci: bump versions of actions in GHA
  ci: update to new API for step outputs in GHA

 .github/workflows/build.yml | 41 +++++++++++++++----------------------
 1 file changed, 17 insertions(+), 24 deletions(-)

-- 
2.37.3


             reply	other threads:[~2022-10-12 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 16:29 David Marchand [this message]
2022-10-12 16:29 ` [PATCH 1/2] ci: bump versions of actions in GHA David Marchand
2022-10-12 16:29 ` [PATCH 2/2] ci: update to new API for step outputs " David Marchand
2022-10-12 16:53   ` David Marchand
2022-10-17 14:01     ` David Marchand
2022-11-14 10:44 ` [PATCH 0/2] GitHub Actions configuration fixes David Marchand
2022-11-14 20:53   ` David Marchand

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=20221012162942.2965188-1-david.marchand@redhat.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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;
as well as URLs for NNTP newsgroup(s).