Once a project is created, you cannot rename it, or even delete it. We should be able to rename a project in the UI without having to ask for support to delete the project, then create it again with the new name.

In some instances it may be that a user makes multiple commits to a branch in a short amount of time, causing multiple Workflows to execute at the same time, possibly deploying in an incorrect order. "Auto Cancel Redundant Builds" may not be suitable for all situations in which multiple deployments are expected. Solution: Enable a way to ensure that commits to a new branch are queued for sequential execution. CCI-I-840

This feature request is to capture those Legacy OAuth users who are interested in migrating to the new GitHub App integration

CircleCI currently offers 400,000 free build credits for open-source projects. Unfortunately, due to the way this is automatically detected and applied, this is only possible for projects hosted on github. To enable open-source projects hosted on gitlab to benefit from the same generous offer the same autodetection method needs to be implemented.

You are able to see all workflows/jobs for a given branch by going to https://circleci.com/gh/{org}/{project}/tree/{branch} such as https://circleci.com/gh/socialtables/ent-killer/tree/master It would be extremely useful to see a list of all tagged jobs/workflows for all tags. We use tags to trigger staging/production builds and have no way of visualizing a record of all workflows/jobs of this type. Added filtering to be able to get workflows that have done a certain step would also be very useful. For us, viewing all workflows that have succeeded job deploy-production would allow us to fully use Circle to manage deploys. CCI-I-621

In some cases environment variables are useful to print out, it would be helpful to be able to whitelist the ones we'd like to show. CCI-I-1223

We have been avid users of CircleCI and truly appreciate the robust continuous integration and continuous deployment (CI/CD) capabilities your platform offers. It has significantly improved our development workflows. We are writing to request an enhancement to CircleCI's GitHub integration, specifically related to handling events when a pull request is merged into the main branch or when a branch is deleted. Currently, CircleCI does not provide native support for these critical events, and we believe that adding this functionality would greatly benefit the developer community. Feature Request Overview: We kindly request that CircleCI consider implementing the following features: PR Merge Event Trigger: Allow CircleCI to automatically trigger workflows when a pull request is successfully merged into the main branch. This would enable us to perform additional automated tasks, such as deployment, testing, or notifications, upon successful merges. Branch Deletion Event Trigger: Enable CircleCI to react to branch deletion events. When a branch is deleted, CircleCI should be able to execute predefined workflows, helping us manage post-branch cleanup, environment deprovisioning, or other necessary actions. Why This Feature Matters: Implementing these features would have several benefits: Automation: It would enhance automation capabilities, reducing the manual intervention required to manage post-merge and post-branch deletion processes. Efficiency: Teams could automate the execution of tasks that were previously done manually, improving efficiency and reducing the risk of human error. Flexibility: Users would have the flexibility to define custom workflows triggered by these events, tailoring CircleCI to their specific needs. Complete CI/CD Workflow: These features would make CircleCI an even more comprehensive CI/CD solution, aligning with modern development practices. Use Cases: PR Merges: Trigger deployments or additional testing when a pull request is merged to ensure code quality and accelerate the delivery process. Branch Deletion: Automate the removal of associated resources, such as staging environments or temporary branches, when they are no longer needed.

Give developers a sense of how much things are costing so if they build a terribly optimised CI process they see it in tangible terms. CCI-I-1079

It would be great if CircleCI allowed you to configure an automatic retry of a build upon failure. Ideally, you would be able to specify the max number of times you would like it to retry. Taken from: https://discuss.circleci.com/t/support-auto-retrying-of-failed-builds/13332/6 CCI-I-935

Currently, GitLab organization are created with the following syntax: > cci-* This can be difficult to discern when there are multiple GitLab organizations. This feature request is to introduce the ability to rename the organization.