| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
no enforced trailing comma on arguments...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
252 Style/TrailingCommaInLiteral
84 Style/TrailingCommaInArguments
15 Style/SpaceAroundKeyword
--
351 Total
We already dealt with SpaceAroundKeyword under its old name
SpaceBeforeModifierKeyword, it looks like it got stricter about
spaces after keywords.
TrailingComma also got split, and it looks like the
TrailingCommaInArguments behavior is new?
|
|
|
|
|
| |
helps to remember the values of expensive things that we go off and
compute.
|
|\
| |
| | |
launchd for osx
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Change shell for locked user.
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | | |
petracvv-route_logic_fix
|
| | | |
|
| | |
| | |
| | |
| | | |
this looks nicer.
|
| | |
| | |
| | |
| | |
| | | |
this is from the same ruleset that we had, but the new code catches more
conditions.
|
| | |
| | |
| | |
| | | |
ensure source is used on all functional tests
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Style/NegatedWhile
Style/ParenthesesAroundCondition
Style/WhileUntilDo
Style/WordArray
Performance/ReverseEach
Style/ColonMethodCall
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
4174 Style/SpaceInsideHashLiteralBraces
1860 Style/SpaceAroundOperators
1336 Style/SpaceInsideBlockBraces
1292 Style/AlignHash
997 Style/SpaceAfterComma
860 Style/SpaceAroundEqualsInParameterDefault
310 Style/EmptyLines
294 Style/IndentationConsistency
267 Style/TrailingWhitespace
238 Style/ExtraSpacing
212 Style/SpaceBeforeBlockBraces
166 Style/MultilineOperationIndentation
144 Style/TrailingBlankLines
120 Style/EmptyLineBetweenDefs
101 Style/IndentationWidth
82 Style/SpaceAroundBlockParameters
40 Style/EmptyLinesAroundMethodBody
29 Style/EmptyLinesAroundAccessModifier
1 Style/RescueEnsureAlignment
|
| | |
| | |
| | |
| | | |
Chocolatey.
|
|\ \ \
| | | |
| | | | |
auto-fixing some easy cops
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
3 Performance/CaseWhenSplat: Place when conditions with a splat at the end of the when branches.
1 Style/ElseAlignment: Align else with if.
1 Style/EvenOdd: Replace with Fixnum#even?.
1 Style/MethodDefParentheses: Use def with parentheses when there are parameters.
3 Style/PercentQLiterals: Do not use %Q unless interpolation is needed. Use %q.
3 Style/SpaceAfterColon: Space missing after colon.
2 Style/SpaceAfterMethodName: Do not put a space between a method name and the opening parenthesis.
2 Style/Tab: Tab detected.
1 Style/TrailingUnderscoreVariable: Do not use trailing _s in parallel assignment.
1 Style/UnneededCapitalW: Do not use %W unless interpolation is needed. If not, use %w.
|
|/ / /
| | |
| | |
| | | |
verbose log info.
|
|\ \ \
| | | |
| | | | |
Copyright and author line update
|
| | | | |
|
| | | |
| | | |
| | | | |
Generated via git ls-files | xargs perl -pi -e "s/(Author.*?<[^@]+@)(?:opscode\\.com|getchef\\.com)(>)/\\1chef.io\\2/gi"
|
| | | |
| | | |
| | | | |
Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./gi"
|
| | | | |
|
| | | |
| | | |
| | | | |
Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"
|
|/ / /
| | |
| | |
| | | |
profiles installed
|
|\ \ \
| |_|/
|/| | |
Add an apt_update resource
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
See chef/chefstyle#11 for analysis and discussion. We select '{}' since
audit of our source code shows that is the most common, and that used to
be the dominant learning paradigm (e.g. in ruby 1.9 pickaxe book.
|
| |
| |
| |
| |
| |
| |
| |
| | |
autocorrects some merges that will be broken when the next
chefstyle is released.
also runs chefstyle after the travis tests, because i'd rather know
how the code is broken rather than how its not pretty.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.
|
| |
| |
| |
| | |
chefstyle -a fixed 1044 occurrances
|
|\ \
| | |
| | | |
Correct uses of fail to raise
|
| | |
| | |
| | |
| | | |
Style/SignalException - 3
|
|/ /
| |
| |
| | |
tests for debug messages when reloading resources
|
|\ \
| | |
| | | |
really fix cops
|
| | | |
|
|\ \ \
| | | |
| | | | |
assert candidates exist for alternate sources and when pinning versions
|