Fedor Korotkov

It didn't work for me actually. You can try to use this branch via `uses: cirrus-actions/rebase@autosquash` (changed `master` to `autosquash`). Closed it until find a better way.

@samholmes thank you for the finding! I've rebased the branch. PTAL.

I think in theory this should work: ```YAML on: issue: types: [labeled] name: Automatic Rebase jobs: rebase: name: Rebase if: github.event.issue.pull_request != '' && github.event.label == 'needs_rebase' # the rest...

@Meshari17 what is the reason behind the revert? Did you see that you can replicate the logic natively with the actions? ```yaml jobs: rebase: name: Rebase if: github.event.issue.pull_request != ''...

I'm not sure if actions have enough permissions to reinstate the approvals from other users. 🤔

This is a weird Actions limitation that one workflow can't trigger another one. See [this community post](https://github.community/t/triggering-a-new-workflow-from-another-workflow/16250/33) for more details. I don't believe there is a viable workaround at the...

In this particular case the reason of the error is a timeout for pulling a Docker image. Windows images are tend to be very large and especially the `cmake` one...

The problem is that Cirrus will need see `ec2:CreateTags` permission (see [7551fd0](https://github.com/cirruslabs/cirrus-ci-docs/commit/7551fd045aee52bc4b64572b15f3d151cfd65a9a)). Otherwise it will break instance scheduling. I've updated the documentation and will reach out to people using Cirrus...

Just added a `deleteRepository` mutation to the [schema](https://github.com/cirruslabs/cirrus-ci-web/blob/master/schema.graphql). Build, log deletion #52 and cache invalidation #379 to follow.

I think in order to implement the self-cleanup mechanism we'll need to create a Kubernetes operator. We can call it `expire`. Such operator will delete objects from Kubernetes based on...