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

Currently uploading artifacts is really slow if there are lots of files - one way round this is to compress all the individual files into a (e.g.) .tar.gz file, and upload that. Sometimes it is useful to have direct access to the individual files however (e.g. .html files), so this approach doesn't work. If there was a way to un-tar the file after it has been uploaded however this wouldn't be a problem. CCI-I-1146

CircleCI Terraform provider would be great addition as it would allow to manage CircleCI projects using code. CCI-I-374

When using the "Run Pipeline" feature, the name of the parameter is currently left blank, and open to incorrect use. It would be useful to pre-populate this with a list of parameters that have been defined within the config file.

Hi, I belive the following scenario is generic and other people will find it useful. Scenario: A mono repo contains git submodules. These submodules are separate git projects (by definition) with their own .circleci/config.yml files and can built/deployed independently. The host repository (monorepo) should be able to build each submodule as a part of its workflow by continuing with submodule projects circleci config files. It would be nice if we could specify which submodule branch to checkout. My attempt I found Path Filtering and Continuation Orbs can't handle the above scenario due to different reasons. My support request: 141996 confirmed the same. Thank you! Regards, Tharaka Manawardhana

Show org-wide concurrency limit somewhere in the Insights dashboard. Currently, this requires CSMs/AEs to manually pull the limit # and send to customers for reference.

Like most engineers, I prefer to use a dark UI. CCI-I-930

Originally asked here: https://discuss.circleci.com/t/auto-cancel-builds-on-default-branch/5536 We would like auto-cancel to apply to the default branch, specifically because we have a deploy action associated with it. The deploy is slow and multiple builds are often racing with each other and we occasionally get an older build that finishes after a newer one, leaving us with older code deployed. (This is only for a staging environment deploy in our case though.) CCI-I-214

Currently the feature to manually trigger a pipeline is not supported with the GitHub Apps integration. This feature request is for the trigger pipelines feature to be supported. If you would like to move from the GItHub OAuth integration to the GitHub Apps integration but are having trouble doing so, please feel free to provide additional feedback for our product team here: https://docs.google.com/forms/d/e/1FAIpQLSfnYhFLjmZ0OP8goemexAvgHDPJqgHyDF1QiIl2HdPktTKvlQ/viewform

The Filter branches drop down should have a "Tagged" option. Tagged builds either get lost in the "All Branches" view or are omitted from specific branch views. Being able to see Just "Tagged Builds" would be incredibly helpful OR even provide a field to allow partial matches for tagged builds (v5.*)