Pre-populate parameter names in "Run Pipeline" feature
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.
Add Support for self-hosted Gitlab instances
CircleCI already support SaaS GitLab. Kindly add Support for self-hosted GitLab instances
Add support for GitHub Draft PRs
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
Don't include on_hold time in duration
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.
Set browser session time limit
Admins should be able to set the browser session time limit for the CircleCI session. This could either be a slider or set limits but admins should be able to set this for security reasons.
Clear error when user on Open Source project attempts to build on their own fork of the repo
Users can experience situations where CircleCI simply does not show up on their PR. It seems like it's a common mistake for contributors to follow their own fork of the project- causing CircleCI to not show up on the PR because it attempts to run as part of the contributor's personal fork. To help them fix this, the open source admin will point users to this trouble-shooting guide: https://support.circleci.com/hc/en-us/articles/360008097173-Troubleshooting-why-pull-requests-are-not-triggering-jobs-on-my-organization- . Though, contributors often still need guidance/assistance and it's also time consuming to always point them to this. It would be helpful if CircleCI would make it more difficult to end up with this bad fork CI setup.
Ability to delete project
It would be great to allow users (depending on permissions) to delete the projects themselves. This is currently not available on the UI and on the API (see https://circleci.com/docs/api/v2/index.html#tag/Project ). See a previous Discuss post here: https://discuss.circleci.com/t/add-ability-to-delete-a-project-from-circleci/936/12 In addition, I wonder if this feature may be something the system offers under privacy.circleci.com .
Support new M1 ARM-based Macs
M1 based macs compile software stack 2x as fast (according to customer). More apps & companies are going to start running on M1 too
Allow more precise times in Scheduled Workflows
Currently, when a scheduled pipeline is scheduled to run at 8 AM, it can be run anytime between 8 AM and 9 AM. https://circleci.com/docs/scheduled-pipelines/#faq It would be good to have the ability to control instead of any time between 8 AM and 9 AM, it could be configured to run anytime between 8 AM and 815 AM.