Event JSON
{
"id": "92ef4f2301cba4aa15338d12abcc9adf558137326a2ad72cb73402281224b208",
"pubkey": "9fbdb8033657b57c24914ec9ec2ce3b15e64456dde535a5ec22cd51c04c7273a",
"created_at": 1731081412,
"kind": 1,
"tags": [
[
"p",
"b65a66f71bfc8fc5882d62b8dae9be52082ee34c7923c56548a175cdf3626b86",
"wss://relay.mostr.pub"
],
[
"p",
"6b21c06c57aca12c8db0107e061b68c1be74bb969cfcd6fb5b2f8fc02bb82ace",
"wss://relay.mostr.pub"
],
[
"e",
"8a44d5575fce851b1d1dddb0d726489d4bb4d67a3b4e037b4c39df1690176010",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.gitea.io/users/gitea/statuses/113448151478188322",
"activitypub"
]
],
"content": "nostr:npub1kedxdacmlj8utzpdv2ud46d72gyzac6v0y3u2e2g596umumzdwrq7y62j2 Good news! There is a current work-around, where you have an \"ignite\" runner that your repo has a trigger workflow for, and when jobs come in, the ignite is always running and will wakeup/create your actual runner for incoming tasks, and then we just merged \"one-shot\" capabilities for the runner so that when the job is complete the runner will stop and your machine can go back to sleep.\n\nWe are working on additional functionality so that this ignite runner isn't needed :)",
"sig": "909650cf19424132ec33c401e252cf23497cb36209317f72b884926e92b8ef497744b9c5ef237eb6ddd05768eebcafaceee586f78326a9921c2da97b090fcf9b"
}