unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: mikadoZero <mikadozero@yandex.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Automated linting before master branch commit
Date: Wed, 27 Mar 2019 09:01:26 -0400	[thread overview]
Message-ID: <cuca7hg5v4p.fsf@yandex.com> (raw)
In-Reply-To: <20190325182412.40b822db@scratchpost.org>


Danny Milosavljevic writes:

> Hi,
>
>> What do people think about automating package linting?  This would be to
>> make sure a package is linted before it is committed to the Guix
>> repository master branch?
>
> A linter by its nature will in some cases flag things which are not wrong,
> otherwise one could just check the stuff while compiling in the first place.
>
>> I am not familiar with what Guix uses for continuous integration /
>> deployment.
>
> We can manually make cuirass and/or Hydra evaluate custom branches--but it's
> not automated.
>
> Christopher Baines is working on making patch review better--see thread
> "Patchwork + automated checking and testing of patches".

Thanks for sharing that thread.

>> Estimated number of packages with autogenerated tarball:
>> 
>> 389
>
> Yeah, those should be updated.  With that many packages, writing a script
> to do it would be less annoying.

      parent reply	other threads:[~2019-03-27 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 16:49 Automated linting before master branch commit mikadoZero
2019-03-25 17:24 ` Danny Milosavljevic
2019-03-25 18:31   ` Ricardo Wurmus
2019-03-27 13:01   ` mikadoZero [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cuca7hg5v4p.fsf@yandex.com \
    --to=mikadozero@yandex.com \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).