Feature Requests

The auto scroll is nice for the steps viewer - except that if you try to scroll while it's auto scrolling, it fights you over and over again. Make the auto scroll faster and stop scrolling it if the user starts scrolling. It's incredibly annoying to try to scroll and have it scroll back like three times every time when I open the steps view

When running pipelines tailored to specific domains, environments, or regional targets within a single repository, identifying the specific context of a run requires digging into workflow details or individual job logs. While our immediate use case involves distinguishing pipelines by jurisdiction (e.g., region/country), this applies broadly to any pipeline metadata. Proposed Solution Introduce a native label (or tags) parameter in the .circleci/config.yml at the workflow level. This label should be rendered prominently in the main Pipelines UI view and provide filtering capability in the dashboard. While region/country is a primary example, workflow labels could be used for any custom categorisation, such as: Target Jurisdiction / Region: US, EU, APAC Environment: staging, production, sandbox Test Scope: e2e, smoke, performance Component / Microservice: auth, billing, notifications Example Configuration (.circleci/config.yml): workflows: run-system-tests: label: US # Proposed key-value or simple string tag jobs: - run-tests UI Mockup / Expected Behavior Pipeline List View: Display a badge next to the commit/pipeline details showing the defined label (e.g., US). Filtering: Allow users to filter the Pipelines view by label or tag values to quickly locate regional test runs or specific deployment targets.

The Linux install docs ( https://circleci.com/docs/install-machine-runner-3-on-linux/ ) add the apt repo by piping packagecloud's install script into bash: curl -sf " https://packagecloud.io/install/repositories/circleci/runner/script.deb.sh?any=true " | bash The packagecloud script runs apt-get update / apt-get install without a dpkg lock timeout, so Ubuntu boot apt-daily / unattended-upgrades may hold the lock and the install will fail intermittently. A curl failure is also silent under | bash, so the repo is never added and the later apt-get install circleci-runner fails. I would like to request that CircleCI: Work with packagecloud.io to make the script retry on dpkg lock contention (e.g. -o DPkg::lock::Timeout=300). Document adding the repo directly as a workaround: curl -fsSL https://packagecloud.io/circleci/runner/gpgkey | gpg --dearmor -o /usr/share/keyrings/circleci-runner-archive-keyring.gpg echo "deb [signed-by=/usr/share/keyrings/circleci-runner-archive-keyring.gpg] https://packagecloud.io/circleci/runner/any/ any main" > /etc/apt/sources.list.d/circleci_runner.list apt-get update && apt-get install circleci-runner

GitHub Actions support on CircleCI is currently available in open preview on Linux resources. Select your GitHub Actions config during project setup. If you run into issues or have feedback please let us know here.

At this time, the Insights API excludes workflows triggered by tag pushes. Adding this feature will allow customers to view workflows, including those triggered by tags via GET /insights/{project-slug}/workflows rather than having to query all pipelines. CCI-I-1413

Letting orgs customize or provide an alias to stock GH App triggers will ease adoption for orgs that having long standing labels embedded in their system. For example, an org may use a Github webhook to trigger a CircleCI build with the ci: run-ci label, configured under a machine user. They would like to ensure that the underlying Github user working on a PR (that could apply label and trigger a build) would be associated as the author of the new pipeline. GH App adoption would solve for this BUT would require the entire org to update their label from ci: run-ci to run-ci for it to work. An easier path to adoption would get orgs to take advantage of new features and functionality.

cannot get any help when I try to make payment. should have a direct support. I try to add a billing account for our company's accountant (who doesn't use github), but she cannot see the settings to make the payment. CCI-I-776

Please add git commit SHA parameter to Trigger Pipeline endpoint along with branch and tag . I have a use case for rollback action to a particular commit. Example payload: { "sha": "ebf73d7382bcc3271f7878434e892ac9142dfa99", "parameters": { "deploy_prod": true } }

We're interested in tagging our CircleCI runners depending on what Github organization and what Github repository the job is running in. We're able to achieve this in self hosted runners via "command_prefix", but for machine provisioner builds, we haven't found a way to do it. If there was a custom script that we could run that can read the CircleCI job environments on machine provisioner builds, this would allow us to create a script to tag the EC2 machine accordingly. This script can live in the machine provisioner runner's AMI.

Unapproved type: approval jobs have no expired/non-determining state; the only way off on_hold is cancel, which marks the entire workflow canceled even when build/test jobs already succeeded. A gate to time out or be declined without driving workflow/pipeline (and Insights) status is needed, so DORA/pipeline health can reflect the jobs that actually ran.