openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <>
Subject Re: code style guidelines
Date Sat, 28 Oct 2017 11:27:13 GMT
Hi John thanks for the PR
You can setup the scancode utility that we use as a pre-commit hook here

It checks for license headers also
The repo is here

We use spaces and other minor code styles as describe in the scancode repo
These include:

On Fri, Oct 27, 2017 at 11:29 PM John Sanda <> wrote:

> I just submitted a very small PR[1] for a CLI issue, and I see that the
> travis build failed due to formatting. I am using emacs, and it is
> configured to run gofmt on save. I really have not done much Go programming
> so I was a bit surprised to learn that gofmt uses tabs instead of spaces.
> Are there style guidelines or conventions documented anywhere? I want to
> make sure that I follow whatever conventions are in place.
> [1]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message