From: Ricardo Wurmus <rekado@elephly.net>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: "Simon Tournier" <zimon.toutoune@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Automatically testing package updates
Date: Thu, 05 Dec 2024 20:58:24 +0100 [thread overview]
Message-ID: <87ldwt7vhb.fsf@elephly.net> (raw)
In-Reply-To: <87ldwu860j.fsf@gmail.com> (Suhail Singh's message of "Thu, 05 Dec 2024 11:10:52 -0500")
Suhail Singh <suhailsingh247@gmail.com> writes:
> If we do decide to keep bots in a separate realm as it were, it would be
> desirable (and in my opinion, important) if that still allowed for at
> least as much transparency that the issue tracker provides for human
> activities.
Examples are the guix-cran and guix-bioc channels:
https://github.com/guix-science/guix-cran
https://github.com/guix-science/guix-bioc
They are generated with these scripts:
https://github.com/guix-science/guix-cran-scripts/
For my purposes this is sufficient transparency. Automated updates for
closed package collections (by team scope or otherwise) would look
similar, I assume.
--
Ricardo
next prev parent reply other threads:[~2024-12-05 19:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 13:44 Automatically testing package updates Ludovic Courtès
2024-12-02 14:50 ` Simon Tournier
2024-12-02 19:14 ` Simon Tournier
2024-12-02 19:16 ` Simon Tournier
2024-12-05 7:20 ` Efraim Flashner
2024-12-05 8:06 ` Hilton Chain
2024-12-05 9:23 ` Ricardo Wurmus
2024-12-05 13:29 ` Suhail Singh
2024-12-05 15:31 ` Ricardo Wurmus
2024-12-05 16:10 ` Suhail Singh
2024-12-05 19:07 ` Attila Lendvai
2024-12-05 19:55 ` Ricardo Wurmus
2024-12-06 5:09 ` Suhail Singh
2024-12-06 4:53 ` Suhail Singh
2024-12-05 19:58 ` Ricardo Wurmus [this message]
2024-12-03 0:32 ` Vagrant Cascadian
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=87ldwt7vhb.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=suhailsingh247@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.