Feature Requests

Would be nice to be able to trigger certain builds or jobs by commenting on a pull request. CCI-I-1213

I added a manual approval "trigger_rollback" job recently to my Circle 2.0 workflow and did not like the UI integration with github. On builds where I did not trigger this optional "trigger_rollback" job, the overall Github status was "Some checks haven't completed yet." (See screenshot.) I talked to CircleCI support and they told me to deselect the status check for a "type: approval" job as described in this github article: https://circleci.com/docs/2.0/workflows-waiting-status/ , which I had already done. I still need the "trigger_rollback" job and corresponding status check. The "trigger_rollback" status check is type:approval, so I want it to be pending but I don't want the overall PR status to be pending -- instead I want the overall PR status to be green and say "All checks have passed." CCI-I-445

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

I would like to run builds on pull requests and on certain tags/branches only. We have processes that only need to run tests on pull requests, but when we deploy to test or staging we would like to push out a tag or branch and have it deploy. Currently It's all or nothing with pull requests and testing. CCI-I-541

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

SARIF: https://sarifweb.azurewebsites.net/ Similar to how you expose test results in the UI/API, it would be great to support more generalized static analysis results. SARIF is a common format that can be used across many languages and tools Github supports SARIF format: https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github

I would like to trigger workflow or build when merging a PR from certain branch. Since CircleCI has already supported conditional workflow and exposed git.branch in the pipeline, I believe this is doable with potential relative low effort if we have access to git.source_branch and git.event_type merge or maybe a simpler or higher-level API to accomplish this. The current workaround provided by support seems to be hacky because it's cumbersome and it has to run workflow, trigger job and make an early exit in conditional step https://discuss.circleci.com/t/how-to-retrieve-a-pull-requests-base-branch-name-github/36911 The alternate workaround is using github action to make REST API to trigger the pipeline in CCI on closed pull_request against target branch with branch filtering of source branch.

As if like Firebase Testlab feature to execute the tests of the app in a physical device, requesting CircleCI to have this feature. Good to have this feature to get the real issues when we run the Automation tests in a physical device rather than a virtual simulator.