From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: GitHub automation for Cygwin builds [Was: Updated: moreutils v0.65-1]
Date: Thu, 10 Jun 2021 18:53:41 +0100 [thread overview]
Message-ID: <f9ad639d-ff2d-619b-53e2-251f88c40e75@dronecode.org.uk> (raw)
In-Reply-To: <01352ece-b288-9e4b-cb40-6754cba06e4a@SystematicSw.ab.ca>
On 06/06/2021 19:32, Brian Inglis wrote:
> On 2021-06-06 11:37, ASSI wrote:
>> Jon Turney writes:
>>> I'd like feedback on what other improvements are needed for this to
>>> become the preferable way to build packages.
>>
>> As long as you have to have a GitHub account to look at the results I
>> won't be able to use it.
>
> Check it out and see if you do:
>
> https://github.com/cygwin/scallywag/actions
Yeah, this complaint is slightly confusingly worded, but if you log out
of github, you get a button which says "Sign in to view logs".
Which is annoying.
> I already have one and it works fine for me: only comment is that the
> log seems less readable than on Appveyor, so harder to spot the issues,
> but that's only an initial impression; will have to check and compare
> with Appveyor logs.
prev parent reply other threads:[~2021-06-10 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+kUOanKdcsMg1oHzTkBaaXxOF-qw+uoF7_w9CvTRgd_hRH-Gg@mail.gmail.com>
2021-01-16 20:33 ` Adam Dinwoodie
2021-01-16 22:31 ` Ken Brown
2021-01-17 5:15 ` Marco Atzeri
2021-01-17 15:33 ` Adam Dinwoodie
2021-05-09 14:40 ` Jon Turney
2021-06-06 17:19 ` Jon Turney
2021-06-06 17:37 ` ASSI
2021-06-06 18:32 ` Brian Inglis
2021-06-10 17:53 ` Jon Turney [this message]
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=f9ad639d-ff2d-619b-53e2-251f88c40e75@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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.
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).