Heartbeat eaten up the most plus bulletin.
How to free github runner from this burden?
We could have a public repo just doing the heartbeat checking cosmos and post issue. Do we need the heartbeat for anything else? Cosmos stuff is secret.
Azure functions not in the free plan.
Logic apps. I think in included.
I would go for a public repo doing the heartbeat. Everyone who needs one registers itself in cosmos with name like crunch. Heartbeat checks. If there are issues for crunch it posts. No llm necessary.
A table with repo URL, nickname would be OK, right? Can do follow up checks, bulletin checks etc.
Only necessary that issues are picked and trigger a run. Maybe with a special label?
Copied from Copilotclaw/brainstorm#58
Heartbeat eaten up the most plus bulletin.
How to free github runner from this burden?
We could have a public repo just doing the heartbeat checking cosmos and post issue. Do we need the heartbeat for anything else? Cosmos stuff is secret.
Azure functions not in the free plan.
Logic apps. I think in included.
I would go for a public repo doing the heartbeat. Everyone who needs one registers itself in cosmos with name like crunch. Heartbeat checks. If there are issues for crunch it posts. No llm necessary.
A table with repo URL, nickname would be OK, right? Can do follow up checks, bulletin checks etc.
Only necessary that issues are picked and trigger a run. Maybe with a special label?
Copied from Copilotclaw/brainstorm#58