[bug#63713] Request for merging "ruby-team" branch

[bug#63713] Request for merging "ruby-team" branch

[Christopher Baines]

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

I'm getting a bit ahead of myself here as I've only just created the
branch, but I'm creating this issue mostly so that I can write and test
qa-frontpage code for finding and processing these "Request for merging"
issues.

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

[bug#63713] Request for merging "ruby-team" branch

[Ludovic Courtès]

Christopher Baines <mail@cbaines.net> skribis:

> I'm getting a bit ahead of myself here as I've only just created the
> branch, but I'm creating this issue mostly so that I can write and test
> qa-frontpage code for finding and processing these "Request for merging"
> issues.

Hi!  So did it process it?  :-)

Ludo’.

[bug#63713] Processing

[Andreas Enge]

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.

Andreas

[bug#63713] Processing

[Christopher Baines]

[-- 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 --]

[bug#63713] Request for merging "ruby-team" branch

[Christopher Baines]

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


Christopher Baines <mail@cbaines.net> writes:

> I'm getting a bit ahead of myself here as I've only just created the
> branch, but I'm creating this issue mostly so that I can write and
> test qa-frontpage code for finding and processing these "Request for
> merging" issues.

I'd like to merge ruby-team this week, I think it's pretty much ready.

There are a few breakages, I'm going to try and make some improvements
to the qa-frontpage to more easily highlight these.

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

bug#63713: Request for merging "ruby-team" branch

[Christopher Baines]

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


Christopher Baines <mail@cbaines.net> writes:

> Christopher Baines <mail@cbaines.net> writes:
>
>> I'm getting a bit ahead of myself here as I've only just created the
>> branch, but I'm creating this issue mostly so that I can write and
>> test qa-frontpage code for finding and processing these "Request for
>> merging" issues.
>
> I'd like to merge ruby-team this week, I think it's pretty much ready.
>
> There are a few breakages, I'm going to try and make some improvements
> to the qa-frontpage to more easily highlight these.

I've pushed the ruby-team changes to master now as
2ccf3eb495eafe4c825a568697dea2630addeeaa.

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