Renaming doWithCommandeer to cfgInit to make clearer what it does and for consistency

[MarkRosemaker]

Regarding my proposal to simplify doWithCommandeer, I found that renaming alone will clear things up.

For one, I realized that there are two different object types:

1. doWithCommandeer func(c *commandeer) error
2. doWithCommandeer func(cfg config.Provider) error

When initializeConfig(mustHaveConfigFile, running bool, h *hugoBuilderCommon, f flagsToConfigHandler, doWithCommandeer func(c *commandeer) error) is called, the last argument is either nil or was named cfgInit.

Therefore, renaming 1. to cfgInit clears things up because it's the only thing it ever does.
I renamed 2. cfgSetAndInit because it sets the Cfg field of commandeer (to a *viper.Viper pointer) and runs cfgInit.

[claassistantio]

All committers have signed the CLA.

[bep]

You need to gofmt your source files. I recommend you use an editor where you can configure this to happen automatically on save. I use LiteIDE where this is default.

[MarkRosemaker]

That's strange. I do have gofmt on save and I now manually ran it. There are no changes to commit.

[bep]

What Go version are you running? We do the "gofmt check" on Travis with Go 1.13 only as they tend to change their format rules slightly from version to version. So if you gofmt with Go 1.12 it could still be "wrong" for Go 1.13.

[MarkRosemaker]

What Go version are you running? We do the "gofmt check" on Travis with Go 1.13 only as they tend to change their format rules slightly from version to version. So if you gofmt with Go 1.12 it could still be "wrong" for Go 1.13.

Fixed it, thanks!

[bep]

OK, the change itself looks good, but can you squash the 3 commits and make a proper commit message (it does not have to be long, important part is the title).

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.