From: Taylor Blau <me@ttaylorr.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 0/4] Avoid using deprecated features in Git's GitHub workflows
Date: Wed, 7 Dec 2022 17:40:16 -0500 [thread overview]
Message-ID: <Y5EWUNbR1X+GrrNs@nand.local> (raw)
In-Reply-To: <pull.1440.git.1670423680.gitgitgadget@gmail.com>
On Wed, Dec 07, 2022 at 02:34:36PM +0000, Johannes Schindelin via GitGitGadget wrote:
> Johannes Schindelin (4):
> ci: use a newer `github-script` version
> ci: avoid deprecated `set-output` workflow command
> ci: avoid using deprecated {up,down}load-artifacts Action
> ci(l10n): avoid using the deprecated `set-output` workflow command
These all look reasonable to me, minus the first one which is already
on 'master' as-is (unless I am missing something, but see my reply to
that email).
Thanks,
Taylor
next prev parent reply other threads:[~2022-12-07 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:34 [PATCH 0/4] Avoid using deprecated features in Git's GitHub workflows Johannes Schindelin via GitGitGadget
2022-12-07 14:34 ` [PATCH 1/4] ci: use a newer `github-script` version Johannes Schindelin via GitGitGadget
2022-12-07 22:22 ` Taylor Blau
2022-12-07 14:34 ` [PATCH 2/4] ci: avoid deprecated `set-output` workflow command Johannes Schindelin via GitGitGadget
2022-12-07 22:24 ` Taylor Blau
2022-12-07 14:34 ` [PATCH 3/4] ci: avoid using deprecated {up,down}load-artifacts Action Johannes Schindelin via GitGitGadget
2022-12-07 14:34 ` [PATCH 4/4] ci(l10n): avoid using the deprecated `set-output` workflow command Johannes Schindelin via GitGitGadget
2022-12-07 22:40 ` Taylor Blau [this message]
2022-12-07 23:58 ` [PATCH 0/4] Avoid using deprecated features in Git's GitHub workflows Junio C Hamano
2022-12-08 5:50 ` Junio C Hamano
2022-12-07 22:42 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y5EWUNbR1X+GrrNs@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).