ratio/copy_from_gocloc.go|29 col 1| [gostyle.getters] Function and method names should not use a "Get" or "get" prefix, unless the underlying concept uses the word "get" (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use "Counts" over "GetCounts". (ref: https://google.github.io/styleguide/go/decisions#getters ): getShebang
ratio/copy_from_gocloc.go|51 col 1| [gostyle.getters] Function and method names should not use a "Get" or "get" prefix, unless the underlying concept uses the word "get" (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use "Counts" over "GetCounts". (ref: https://google.github.io/styleguide/go/decisions#getters ): getFileTypeByShebang
ratio/copy_from_gocloc.go|71 col 1| [gostyle.getters] Function and method names should not use a "Get" or "get" prefix, unless the underlying concept uses the word "get" (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use "Counts" over "GetCounts". (ref: https://google.github.io/styleguide/go/decisions#getters ): getFileType
ratio/copy_from_gocloc.go|31 col 5| [gostyle.nilslices] When designing interfaces, avoid making a distinction between a nil slice and a non-nil, zero-length slice, as this can lead to subtle programming errors. This is typically accomplished by using len to check for emptiness, rather than == nil. (ref: https://google.github.io/styleguide/go/decisions#nil-slices ): ret != nil
ratio/copy_from_gocloc.go|40 col 5| [gostyle.nilslices] When designing interfaces, avoid making a distinction between a nil slice and a non-nil, zero-length slice, as this can lead to subtle programming errors. This is typically accomplished by using len to check for emptiness, rather than == nil. (ref: https://google.github.io/styleguide/go/decisions#nil-slices ): ret != nil
report/report.go|586 col 3| [gostyle.dontpanic] Don't use panic for normal error handling. Use error and multiple return values. (ref: https://go.dev/wiki/CodeReviewComments#dont-panic )
datastore/artifact/artifact.go|56 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/gcs/gcs.go|14 col 6| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): GCS
datastore/gcs/gcs.go|45 col 6| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/gcs/gcs.go|54 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/mackerel/mackerel.go|82 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/local/local.go|55 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/s3/s3.go|59 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/bq/bq.go|19 col 6| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): BQ
datastore/bq/bq.go|127 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/github/github.go|48 col 1| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/datastore.go|36 col 2| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): GCS
datastore/datastore.go|57 col 2| [gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS
datastore/datastore.go|232 col 1| [gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): datastore<-[To]->NeedToShrink