Allow import for external .codeclimate.yml configurations

[GarreBrenn]

I am working on triggering code quality tests on multiple GitLab repositories from the CI/CD flow of a single GitLab project. We have decided on a .codeclimate.yml configuration that should work for all of our projects. It would be nice to not have to physically copy that configuration into every single project we intend to test, as there are likely 100+ and manually updating these in the case of a change to our default configuration would be quite cumbersome.

While it's documented that you can use external configurations for engines, I don't see any documentation relating to using external .codeclimate.yml files. It would be great if we could instead include a configuration file like:

# here you can see the ability to include several configurations 
prepare:
  fetch:
  - url: "https://raw.githubusercontent.com/thoughtbot/guides/master/.codeclimate.yml"
    path: ".codeclimate.yml"
    name: cc_config_1
  - url: "https://raw.githubusercontent.com/thoughtbot/guides/feature/.codeclimate.yml"
    path: ".codeclimate.yml"
    name: cc_config_2

# here you could specify which codeclimate configurations you would like to enable
codeclimate:
  cc_config_1
    enabled: true
  cc_config_2
    enabled: false

# below here would add to or override the included configuration
plugins:
...

I apologize if this feature already exists, but if it does, this could serve as a reminder that the documentation is unclear.

[filipesperandio]

@GarreBrenn would this work for you? https://docs.codeclimate.com/docs/delegated-analysis-configuration

[GarreBrenn]

@filipesperandio Thank you for your reply! While I am a little embarrassed I didn't see that documentation earlier, I do still think this feature set up the way I mentioned above could be valuable. Since Code Climate is offered via GitLab's Code Quality, it would nice to simply reference another configuration from within the .codeclimate.yml file instead of creating a Code Climate account and managing things that way so my team only has to interact with GitLab. Also this would help minimize the number of API calls users would have to write. What do you think?

[brynary]

Hello -- Thank you for this GitHub issue.

We are going to be releasing a new version of our code quality CLI shortly, and so I am in the process of closing all open GitHub issues in preparation for that. We will be in touch soon and would be happy to hear from you on any feedback you have on the new CLI when it is available later this month.