CircleCI Ideas

Allow for YAML branch locking on PRs

CodeCov has a yaml feature that restricts the modification of the YAML file, and overrides modifications to the PR file. This would mean, in the case of Circle, all PRs would build off of the main branch YAML when this was specified, allowing branches that are behind to inherit changes if any.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 31 2018
  • Not planned
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    March 02, 2018 22:32

    Our general approach is likely to be in the future to allow more dynamic specification of configuration and cross-project triggers of some kind rather than attempting to lock editing of the config itself. The larger goal is to provide a way to have more central control in certain cases over what is run in the system rather than specifically locking down editing of a given branches configuration. The ability for an individual developer to run what they want to run within their own branch/execution sandbox is fairly fundamental to the system, but adding to that the ability to centrally manage configurations outside the control of individual developers is something we've seen in a few different scenarios.