Caching Docker steps about automerge-action HOT 5 CLOSED

The action is now a JS action and no longer uses Docker now (see #125 and #135) so I will close this 😊

from automerge-action.

Relevant discussion: #24

from automerge-action.

Do we have to use docker to run this? Why not make this action run as nodejs ?
See this example.

I'm on a large team with many events that trigger this action and it's starting to cost us a lot (it's about 10K actions per day) which is absurd. I think changing this to a nodejs action will improve it.

from automerge-action.

Yes, changing this action to use nodejs directly would be a viable option, I think. The release process will be a bit more complicated, though, since the npm dependencies need to be added. But I will have a look into this!

However, at about 10k action invocations per day, I suggest you maybe consider changing this to use "schedule" events instead: even if you set it to run once every minute, it will "only" be around 1500 invocations per day (the invocations might each take a bit longer, though, but I think this will still use fewer action minutes, overall)

from automerge-action.

What I'm experiencing is a large amount of "status" events which is unclear what is their origin it seems that be duplicating x6-7 times (per developer) I'm not sure why is that. I suspect that because we have a CircleCI flows that build around 30 components per commit (we have a monorepo) that might cause the issue, though I don't see 30x status events per commit.

from automerge-action.