Support per user and per repo configurations #8
Labels
Comments
bradleyfalzon
added a commit
that referenced
this issue
May 17, 2017
Users should be able to apply per repository configuration for GopherCI via a config file in the repository, this allows non-admin users to modify GopherCI on a per repository basis if they have write access. Which practically means users can also have their pull request modify GopherCI if they require additional packages to be installed (for cgo for example) or if they want to modify the tools being run. We achieve this by including a YAMLConfig which implements a configReader interface, an interface was chosen primarily to keep tests simpler, but the analyser doesn't really care where the config came from, just that it's able to receive one. The YAMLConfig should be preloaded with the global settings and then it should filter the config based on reading the repository's config file, and finally returning the config to analyser to use. Relates #8.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a user, I should be able to configure which checks run across all my repositories as well as support a per repository configuration (perhaps via
.gopherci.yml- so anyone with write access to the repo, or sending a PR could correctly configure the installation).I may also want to ignore failures that occur within the vendor folder, but this may be a global setting for the installation.
Relates to #3.
The text was updated successfully, but these errors were encountered: