Hi Chris,
On Thu, 28 Aug 2025 at 14:17, Christopher Baines <[email protected]> wrote:
> It isn't obvious to me what the best approach is though, maybe ordering
> branches to be merged could be handled through Pull Requests, or maybe
> we could put in place a generated branch system, where the changes in
> Pull Requests can be grouped together through a Milestone and ordered
> via the Pull Request Dependencies, which I think could have some key
> advantages. A comprehensive plan for the minimal viable approach is
> needed though.
Well, the Milestone appears appealing. For instance, if the title is
standardized and contains the term ’Request’, then:
curl -X 'GET' \
'https://codeberg.org/api/v1/repos/guix/guix/milestones?state=open&name=Request'
\
-H 'accept: application/json'
returns the list of Milestones matching the state and the term.
However, then the API does not provide a mean, to my knowledge, to
access to the list of PRs associated to the Milestone; we only access to
the integer number of still open or already closed PRs.
That said, let list all the PRs
curl -X 'GET' \
'https://codeberg.org/api/v1/repos/guix/guix/pulls' \
-H 'accept: application/json'
then querying for each, e.g., here #2145
curl -X 'GET' \
'https://codeberg.org/api/v1/repos/guix/guix/pulls/2145' \
-H 'accept: application/json'
and the return provides many information including the field ’milestone’
which helps to know if the issue is part of a milestone or not.
If we think larger than Build Coordinator and the Bordeaux build farm,
it could be nice that the approach would also be implementable via
Forgejo actions or else.
And from my understanding, Forgejo actions does not see ’milestone’.
Maybe I’m missing something…
The main advantage of Milestone seems to be a way to have a kind of
“build trains” [1,2].
Cheers,
simon
1: https://docs.gitlab.com/ee/ci/pipelines/merge_trains.html
2: Naming “build train” instead of “merge train”?
Simon Tournier <[email protected]>
Mon, 09 Sep 2024 19:28:57 +0200
id:[email protected]
https://lists.gnu.org/archive/html/guix-devel/2024-09
https://yhetil.org/guix/[email protected]
