To reduce data transfer, it would be nice to specify a region to run all builds from. We only deploy to us-east-1 so running everything in that region would speed up ECR pushes and pulls. I'm guessing this would help with docker_layer_caching as well. CCI-I-241

When a project is configured to use OIDC, it should be possible to use these credentials to pull a private images from ECR [1] when starting up the executor. Projects with OIDC enabled [2] currently still require static AWS keys for ECR image pulls. [1] https://circleci.com/docs/2.0/private-images/#aws-ecr [2] https://circleci.com/docs/2.0/openid-connect-tokens/

GitHub released Draft PRs https://twitter.com/github/status/1096093162345508864 We have users requesting we add support to not run against branches without a Draft PR, creating this feature request to gauge interest and inform prioritization. It would be nice to have the option to run CI only on PRs which are not draft PRs, as they are intended as work in progress and are likely to be in a broken state which is expected. The option to force trigger a build on such requests with an API call will be nice to so that developers can develop their own integrations like running CI on a comment in such a PR. And CI should be triggered as soon as the PR is marked as ready for review (not a draft anymore). CCI-I-883

There isn't a streamlined process for transferring contexts between orgs.

It would be great to see the disk space usage like we see for CPU and RAM consumption on the resources tab to confirm if the executor is running out of disk space.

I don't see a way with default pipeline parameters, API or built-in environment variables to acquire the organization name that a job is running in (at least, not _easily_). One environment variable, CIRCLE_BUILD_URL, contains the project slug afaict, but the organization name would need to be parsed out of this. Could you expose this metadata as CIRCLE_ORGANIZATION, etc.?

Currently, OIDC is is not supported for GitHub. This feature request is for OIDC CircleCI to support OIDC for GitHub.

We have parallelism set to 28 to run our tests. If a single parallel run fails, we currently have to rerun the entire job. It would be great to just re-run the parallel run that failed. CCI-I-1329

At the moment, if a workflow includes an approval step, then the time it spends waiting on_hold is included in the duration. This makes it hard to do any analysis based on the time that the workflow is actually working. For example, the "trend" indicators displayed next to the duration are essentially useless because the on_hold time can be significantly different between one job and the next. It can also be significantly longer than the duration of the actual working time, meaning that increases in the working time are hard to spot.

We would like the ability to set default global build settings that all new projects can inherit. For example, we always want "Pass secrets to builds from forked pull requests" to be "Off" for all new projects. We are now setting this manually, but if we forget to do so, there are serious security consequences. CCI-I-1363