Re: [RFC] On sending forge pull request discussions to the mailing list

On 08/04/2026 18:42, Ben Boeckel wrote:
> On Wed, Apr 08, 2026 at 14:59:07 +0100, Richard Earnshaw (foss) wrote:
>> Isn't that limited to one result though?  What if there were multiple
>> CIs running.  They would need to collude in order to update that.
> 
> Not AFAIK. As long as the context is different, it should be a separate
> status item when rendered. If the context is the same, the status is
> updated with any new description, state, and/or target URL. At least if
> it works anything like GitHub and GitLab's analogous APIs.
> 
> So Linaro CI could send a "pending" status when it first gets the job to
> indicate that it is working and then update with a new state once it
> completes. There may be size limits on description as it usually shows
> up as a tooltip (on GitLab at least) and the target URL is the
> destination when clicked.
> 
> --Ben

Oh, I see.  I'd missed the 'context' field giving the option for multiple reports.

Yes, I think that could work.

Thanks for the pointer.

R.