repo-template-go

Repository template for Go repos under github.com/ianlewis

This repository template is maintained for use in repos under github.com/ianlewis. However, it can be used as a general purpose Go repository starter template.

Usage

1. Update go.mod

   The module directive in go.mod must be updated to the correct module name. The go directive sohuld be updated to the required Go version.

   module github.com/user/repo
   
   go 1.23.2
   

Makefile

The Makefile is used for managing files and maintaining code quality. It includes a default help target that prints all make targets and their descriptions grouped by function.

repo-template$ make
repo-template Makefile
Usage: make [COMMAND]

  help                 Shows all targets and help from the Makefile (this message).
Tools
  license-headers      Update license headers.
  format               Format all files
  md-format            Format Markdown files.
  yaml-format          Format YAML files.
Linters
  lint                 Run all linters.
  actionlint           Runs the actionlint linter.
  markdownlint         Runs the markdownlint linter.
  yamllint             Runs the yamllint linter.

Formating and linting

Some Makefile targets for basic formatters and linters are included along with GitHub Actions pre-submits. Versioning of these tools is done via the requirements.txt and packages.json. This is so that the versions can be maintained and updated via dependabot-like tooling.

Required runtimes:

• node: Node.js is required to run some linters and formatters.
• python: Node.js is required to run some linters and formatters.

The following tools need to be installed:

• actionlint: For linting GitHub Actions workflows.
• shellcheck: For linting shell code in GitHub Actions workflows.

The following tools are installed locally:

• yamllint: For YAML (e.g. GitHub Actions workflows). (installed in Python virtualenv .venv).
• prettier: For formatting markdown and yaml (installed in local node_modules).
• markdownlint: For linting markdown (installed in local node_modules).

Makefile targets and linter/formatter config are designed to respect .gitignore and not cross git submodules boundaries. However, you will need to add files using git add for new files before they are picked up.

Makefile targets for linters will also produce human-readable output by default, but will produce errors as GitHub Actions workflow commands so they can be easily interpreted when run in Pull-Request status checks.

License headers

The license-headers make target will add license headers to files that are missing it with the Copyright holder set to the current value of git config user.name.

Files are checked for the existence license headers in pre-submits.

Project documentation

This repository template includes stub documentation. Examples of CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md can be found in the ianlewis/ianlewis repository and are maintained in line with GitHub recommended community standards.

Security & Dependencies

In general, dependencies for tools and GitHub Actions are pinned to improved overall project supply-chain security.

External dependencies on GitHub actions are limited to official GitHub-owned actions to minimize exposure to compromise of external repositories.

Contributing

See CONTRIBUTING.md for contributor documentation.