Documentation on the impact of a "Dummy commit" about keepalive-workflow HOT 8 CLOSED

There is no cons for doing dummy commits. It won't change any file it just creates an empty git entry.

from keepalive-workflow.

On the plus side this dummy commit will keep your cron based triggers running. I hope that instructions on the readme is enough for most people to find this project. Feel free to improve the documentation if you have any ideas. @jackdomleo7

from keepalive-workflow.

Yeah, I've been using that snippet for over 2 years now - xmonad/X11@a416159

from keepalive-workflow.

Thanks for confirming @liskin, this is a good approach. I will also make it a part of this workflow and provide APIs to opt into this approach.

from keepalive-workflow.

Maybe it was just me getting confused. I think the documentation is fine for now. I'll close the issue. Thanks for the response!

from keepalive-workflow.

There is no cons for doing dummy commits. It won't change any file it just creates an empty git entry.

Which creates noise in git history and makes the project seem more active than it truly is. Not exactly "no cons", IMO.

I mean, most people probably don't care, but if anyone does, there is an alternative that doesn't use dummy commits: https://github.com/liskin/gh-workflow-keepalive

from keepalive-workflow.

@liskin 👍🏻 thanks, that also looks like a good approach. When I wrote this action, there was no such API. Btw have you tested it in the long term (60 days)? Is it keeping the workflow alive?

from keepalive-workflow.

Just released a new version with API Keeplaive.

from keepalive-workflow.