Currently if you run a claude code action for let's say configurable 25min timeout if it didn't complete the task the next run would have to do all of it all over again (waste of tokens), because the changes were not pushed to remote (ephemeral - everything gets wiped out).
Not ideal, ideally I would like to have the changes pushed to a remote WIP draft PR, so I can continue the work with claude code action from there.
I have already a setup like this where I've implemented an extra job with always() trigger to ensure the changes are pushed to WIP draft PR.
I think this should be a built-in feature rather than an hack from the consumer side.
AC's
Currently if you run a claude code action for let's say configurable 25min timeout if it didn't complete the task the next run would have to do all of it all over again (waste of tokens), because the changes were not pushed to remote (ephemeral - everything gets wiped out).
Not ideal, ideally I would like to have the changes pushed to a remote WIP draft PR, so I can continue the work with claude code action from there.
I have already a setup like this where I've implemented an extra job with always() trigger to ensure the changes are pushed to WIP draft PR.
I think this should be a built-in feature rather than an hack from the consumer side.
AC's