The R programming language is a rapidly developing language which gained lots of new users in the last years. Coming from the statistical field, its scope has expanded nowadays. Especially the usage in an academic context increased in the last ye...

Github PRs show if the PR branch has conflicts with the base branch. CircleCI shows test results on the PR branch. What is missing is the ability to see whether test results fail when the PR branch is merged into the base branch. Admittedly, it...

Add support in machine executor and remote docker for Docker version 19.03

Currently, any merges to master trigger all steps of all workflows. In an monorepo that houses multiple projects, this results in multiple redundant steps as, for example, the backend is re-tested and re-deployed even if only frontend changes have...

There are three patterns canceling the build, the first is Auto-cancel redundant builds , and the second is API and the last is Service issue . If a build is canceled the UI should explain why and who/what canceled it.

Secrets may be accidentally printed in the build logs. Travis hide them in the logs masking them as [secret] every time that it finds a match with the provided secrets. See https://discuss.circleci.com/t/masking-secrets-in-output-logs/22231

For many reasons, it is necessary to determine the branch target pull request that triggered the current workflow. This has been a frequently requested feature, and has cropped up on the discuss.circleci site in numinous requests and formats. ...

Circle CI should generate a new build when a pull request is opened on github. The current implementation uses the branch's most recent commit result, instead of generating a brand new build. Consider the following situation. 1) An engin...

Otherwise how are we supposed to cancel builds?

We often end up queuing waiting for executors for our jobs. To fix this we'd like to be able to confirm our project to prioritise branches, e.g. master branch always takes priority over other branches