Feature Requests

Offline instances will eventually be removed from a resource class's instance list in the UI but it would be helpful to be able to remove individual instances and/or purge the entire list.

The Plans page has a UI with a lot of useful information regarding credit utilization, user, network and storage usage information. It will be nice to fetch these information via an API for reporting purposes.

In the UI to see flaky test data a workflow and a branch needs to be selected on the Tests tab in insights. This makes it difficult to attribute flakiness across the project and track that flakiness over time. It would be helpful if there was flaky test information about a project at a glance and if that could be drilled down into without needed to select specific branches first.

Presently the available build minutes in organisations are only available to BB/GH admins. However, it is often team members who bring in a CI solution. My recent experience has been to spin up some CI solutions on the free tier, in the hope that the reliability improvements brought in by effective CI encourage a business case to be made around CircleCI. Part of this initial free tier experience is keeping an eye on build minutes, so that the team do not run out mid-month. I don't think it is secret information and there would be no reason to withhold it from non-admins. CCI-I-881

Is it possible to configure the tool with Amazon Bedrock?

Having an option in between a full checkout and a blobless checkout would be helpful for situations where comparing the previous commit or a single file is needed , but not the rest of the data.

This feature request is to create an allowlist for users to add automated code updating tools and bot users (such as dependabot) to work while utilizing the Prevent unregistered user spend toggle.

Suggestion to add a tag or custom field to projects in CircleCI so that we can group projects by chargeback budget and improve cost/consumption reporting.

We want our team to be able to trigger a build using context. However, they should not be able to view or retrieve this context in anyway.

With increased popularity of lerna / yarn workspaces monorepos, support for things like this seems to be a must: save_cache: key: core-dependencies-{{ checksum "yarn.lock" }} paths: - node_modules - packages/*/node_modules CCI-I-239