Hi Carlos, thanks for your reply!
We're not working with the trunkbot currently (but we do plan to integrate it soon). We're trying to implement a policy of weekly super-stable releases that have been rigorously tested, thus we have an additional /release branch that /main merges into.
I'm currently making a custom mergebot, where whenever a changeset is marked as ready, the bot will merge the /main branch into the /release branch for other teams at our company to xlink to. The bot will also look at the comments of the changesets in /main and create release notes for other developers to read. The way I initially wanted it to work is for the bot to listen for a changeset in /main to have it's "release_status" attribute set to "ready", and it will merge that into main. It will also look at the comments of every changeset from the "ready" changeset all the way back to the previously released changeset (marked as "released") and generate release notes from there. When it's done, it'll mark the initial changeset as "released" and potentially label it.
If the WebSocket only announces the fact that a branch's attribute is changed, I guess I could instead make the mergebot poll the server to check for attribute changes? Or perhaps we're going about this all wrong. Either way, let me know.