unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "Andreas Enge" <andreas@enge.fr>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 63713@debbugs.gnu.org
Subject: [bug#63713] Processing
Date: Fri, 09 Jun 2023 17:31:40 +0100	[thread overview]
Message-ID: <87pm64zjaq.fsf@cbaines.net> (raw)
In-Reply-To: <ZIMih1ZKGCSLv4oI@jurong>

[-- Attachment #1: Type: text/plain, Size: 699 bytes --]


Andreas Enge <andreas@enge.fr> writes:

> It looks so, on
>    https://qa.guix.gnu.org/
> the top two branches, tex-team and ruby-team, are now tagged with the issue
> number. I suppose that also the ordering is not random.

Indeed. There's already some code in the qa-frontpage to look for these
issues and order them, but currently it just uses the date of when the
issue was submitted.

Now that Mumi exposes the blocking information through the GraphQL
endpoint, I need to get the code to use that as well.

I'm not sure if these Ruby changes are what we'll want to merge after
tex-team, maybe tex-team-next or gnome-team are better candidates, but
we can discuss that once tex-team is merged.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2023-06-09 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25  7:59 [bug#63713] Request for merging "ruby-team" branch Christopher Baines
2023-06-08 21:00 ` Ludovic Courtès
2023-06-09 13:00 ` [bug#63713] Processing Andreas Enge
2023-06-09 16:31   ` Christopher Baines [this message]
2023-07-03 11:38 ` [bug#63713] Request for merging "ruby-team" branch Christopher Baines
2023-07-10  7:28   ` bug#63713: " Christopher Baines

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=87pm64zjaq.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=63713@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=ludo@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).