Adding first example

[chrislovecnm]

This PR includes the source code for the tutorial that is hosted here: https://bazel-contrib.github.io/SIG-rules-authors/go-tutorial.html

The code for the above HTML is on the gh-pages branch of the SIG-rules-authors repository:
https://github.com/bazel-contrib/SIG-rules-authors/tree/gh-pages

This tutorial source code includes:

• basic go rules support
• a basic cobra CLI application
• unit test
• Gazelle support

After this PR is finalized, I will update the tutorial markdown.

We are also adding CI/CD for the example. This PR modifies the
presubmit.yml file. This project also uses the words file that
requires the installation of "wamerican", and we are installing that
package during CI/CD.

Fixes: #3316

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[chrislovecnm]

So we are having issues with the CLA, which we have, but I use an alias email and not my login email (security). Secondly, I don't understand why CI is running in the examples directory 🤔 - It is running in the wrong directory.

(16:51:43) ERROR: Analysis of target '//examples/go-code-tutorial:go-code-tutorial' failed; build aborted: no such package 'cmd': BUILD file not found in any of the following directories. Add a BUILD file to a directory to mark it as a package.
--
  | - /workdir/cmd

@fmeum @alexeagle

[fmeum]

So we are having issues with the CLA, which we have, but I use an alias email and not my login email (security).

Could you sign the CLA again, this time with your alias? That's going to be the easiest solution by far as we don't control the CLA checks and would otherwise need to get Googlers involved.

Secondly, I don't understand why CI is running in the examples directory thinking - It is running in the wrong directory.

Adding examples to the top-level .bazelignore should help.

[chrislovecnm]

We have a corporate CLA, and my email is set to my alias - we may need to get a googler involved. I may try another PR with the GitHub hidden email 🤔

[fmeum]

Yes, please try changing your committer email first. If that doesn't work, I can ping someone.

[alexeagle]

when you add a nested workspace, you need to exclude that folder from the outer workspace, Bazel does not do that automatically. You should add examples to .bazelignore

(note, it also excludes it to add a local_repository pointing the outer workspace to the inner one, but IMO that introduces what appears like a load-bearing edge in the graph where it's actually dead code)

[chrislovecnm]

@fmeum I have the correct email address matched to the commit. So I am not certain why the Google CLA machine is not happy

[chrislovecnm]

@fmeum so the CI passed, but of course, it did not test the code. How do we get CI to do a bazel call in another dir?

[fmeum]

@chrislovecnm Your committer email is [email protected]. Are you sure you signed the CLA for that using your current GitHub account and have that email visible? If not, does this help:

You may have Keep my email address private enabled. Without a visible email address, the CLA cannot be checked. Uncheck it and re-create the offending commit, or have your CLA point of contact add your @users.noreply.github.com address to the CLA group.

You can add a new task to presubmit.yml and use the working_directory setting (see https://github.com/bazelbuild/rules_go/blob/d517cd9bec43f0541b421315fe633cdd0f204270/.bazelci/presubmit.yml#L30 for an example).

[chrislovecnm]

@fmeum awesome I will do that. I do need someone from Google to check on the CLA. I have set it up six ways sideways :(

[alexeagle]

Squashing to a single commit might make it easier, since all of them need to pass the validation

[chrislovecnm]

@fmeum and @alexeagle PTAL!

[fmeum]

Looks pretty good to me, just left a few comments. I would also like to have @alexeagle take a look before merging.

[chrislovecnm]

@alexeagle PTAL

[alexeagle]

LGTM

@fmeum want to squash & merge it?

[fmeum]

Looks good to me as well, thanks @chrislovecnm!