Feature Requests

Sometimes it's handy to upload many small artifact files e.g coverage reports. This runs in serial and is very slow compared to uploading one large file.As an example, my coverage reports are 8mb/400 files. On my last build 36s was spent uploading artifacts out of a total 1:23 for the whole build.See more: https://discuss.circleci.com/t/uploading-artifacts-recursively-is-exceptionally-slow/14558 CCI-I-745

Add events relating to the Rerun with SSH feature such as user to the self-serve audit log

Yes, the automatic signup with GitHub is convenient to CircleCI, but my security conscious starts to feel unease and I feel very unsure about what access CirculeCI really have. Does circleCI now have direct access to all my GitHub repos?What if I don't want CircleCI to have a default access to all my repositories? I wished i could signup as a normal user, and then manually add and give access to individual repositories, so I can feel more confident that circleCI only can see the repositories that it should see and nothing else. Basically, I want to apply the law of least privilege here. CCI-I-791

We would like to see CircleCI use the newer GitHub API to lessen the privileges needed for integration.I see that when linking GitHub with CircleCI you still require write access to pretty much everything in my GitHub account.I know, that in the past this was do to a limitation of GitHub OAuth scopes, but now that they have GitHub Apps which allows more granular permission, I would appreciate if I could specify a lower privileged access so that CircleCI cannot arbitrarily modify code in GitHub.New API should allow much more granular access so that by default you don’t get write access. I see this as a real differentiator when picking the most secure CI SAAS. CCI-I-50

Larger applications can sometimes run out of disk space on the macOS executors, it would be great to be able to have the option to expand disk space when needed. CCI-I-1542

An image for the Windows executor that uses Windows Server 2022 (or Windows 11)

As of 18.09, docker daemon supports a new features called build kit. Currently (at least on Enterprise) the daemon does not have the feature flag set to enable build kit. It would be nice if Circle would support build kit going forwards https://docs.docker.com/develop/develop-images/build_enhancements/ CCI-I-1003

Add support for Windows CCI-I-633

Add Mattermost as an option to send webhook notification or some generic webhook CCI-I-999

The highest version that you support is 10 and I am on 11.6. CCI-I-1330