[RFC] On sending forge pull request discussions to the mailing list
Richard Earnshaw (foss)
Richard.Earnshaw@arm.com
Tue Apr 7 13:04:18 GMT 2026
On 02/04/2026 21:23, Ben Boeckel wrote:
> On Thu, Apr 02, 2026 at 11:18:39 +0200, Christophe Lyon wrote:
>>> One thing to add: the linaro bot currently updates existing comments so
>>> it will be good to figure out which messages are a "final state" and
>>> either make the bot recognize them or mark them with <!-- bmm:send -->.
>>
>> Hmmm thanks to your help & suggestions a few months ago I managed to
>> reduce the amount of comments generated by the Linaro bot using these
>> HTML markers/comments: now it updates comments in place when the status
>> changes (pending/running/completed).
>> How to detect a comment is the final one I'm not sure (if there's a
>> crash during the "running" phase, there will probably never be a
>> "completed" update).
>
> Can Linaro bot not submit a custom status to the CI metadata rather than
> a comment? (I'm more familiar with GitLab than Forgejo.)
>
> --Ben
I suspect the best solution would be if we could re-implement the Linaro bot as a runner. But there are security implications that would need to be investigate for that, since the runner would then be managed by the forge (sent jobs), but would be in a separate administrative/security domain.
R.
More information about the Gcc
mailing list