forked from empierre/MyDomoAtHome
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.codeclimate.yml
96 lines (78 loc) · 2.99 KB
/
.codeclimate.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
# This is a sample .codeclimate.yml configured for Engine analysis on Code
# Climate Platform. For an overview of the Code Climate Platform, see here:
# http://docs.codeclimate.com/article/300-the-codeclimate-platform
# Under the engines key, you can configure which engines will analyze your repo.
# Each key is an engine name. For each value, you need to specify enabled: true
# to enable the engine as well as any other engines-specific configuration.
# For more details, see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform
# For a list of all available engines, see here:
# http://docs.codeclimate.com/article/296-engines-available-engines
engines:
# to turn on an engine, add it here and set enabled to `true`
# to turn off an engine, set enabled to `false` or remove it
rubocop:
enabled: true
golint:
enabled: true
gofmt:
enabled: true
eslint:
enabled: true
csslint:
enabled: true
# Engines can analyze files and report issues on them, but you can separately
# decide which files will receive ratings based on those issues. This is
# specified by path patterns under the ratings key.
# For more details see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform
# ratings:
# paths:
# - app/**
# - lib/**
# - "**.rb"
# - "**.go"
# You can globally exclude files from being analyzed by any engine using the
# exclude_paths key.
#exclude_paths:
#- spec/**/*
#- vendor/**/*
# This is a sample .codeclimate.yml configured for Engine analysis on Code
# Climate Platform. For an overview of the Code Climate Platform, see here:
# http://docs.codeclimate.com/article/300-the-codeclimate-platform
# Under the engines key, you can configure which engines will analyze your repo.
# Each key is an engine name. For each value, you need to specify enabled: true
# to enable the engine as well as any other engines-specific configuration.
# For more details, see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform
# For a list of all available engines, see here:
# http://docs.codeclimate.com/article/296-engines-available-engines
engines:
# to turn on an engine, add it here and set enabled to `true`
# to turn off an engine, set enabled to `false` or remove it
rubocop:
enabled: true
golint:
enabled: true
gofmt:
enabled: true
eslint:
enabled: true
csslint:
enabled: true
# Engines can analyze files and report issues on them, but you can separately
# decide which files will receive ratings based on those issues. This is
# specified by path patterns under the ratings key.
# For more details see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform
# ratings:
# paths:
# - app/**
# - lib/**
# - "**.rb"
# - "**.go"
# You can globally exclude files from being analyzed by any engine using the
# exclude_paths key.
#exclude_paths:
#- spec/**/*
#- vendor/**/*