Skip to content

Latest commit

 

History

History
89 lines (62 loc) · 2.58 KB

CONTRIBUTING.md

File metadata and controls

89 lines (62 loc) · 2.58 KB
Raw

Contributing

Here's some ways to help:

  • Try using gojekyll on your site. Use this as fodder for test cases.
  • Choose an item to work on from the issues list.
  • Search the sources for FIXME and TODO comments.
  • Improve the code coverage.

If you choose to contribute code, please review the pull request template before you get too far along.

Developer Cookbook

Set up your machine

Fork and clone the repo.

Install go. On macOS running Homebrew, brew install go is easier than the linked instructions.

Install package dependencies and development tools:

make setup
go get -t ./...

Install golangci-lint. On macOS: brew install golangci-lint

Test and Lint

make test
make lint

Debugging tools

gojekyll -s path/to/site render index.md              # render a file to stdout
gojekyll -s path/to/site render /                     # render a URL to stdout
gojekyll -s path/to/site variables /                  # print a file or URL's variables
gojekyll -s path/to/site variables site               # print the site variables
gojekyll -s path/to/site variables site.twitter.name  # print a specific site variable

./scripts/gojekyll is an alternative to the gojekyll executable, that uses go run each time it's invoked.

Benchmarks

Benchmarks are listed in the file ./docs/benchmarks.md.

As of 2022-02, I use hyperfine for benchmarking. (I don't remember what I used for previous benchmarks.)

The "single-threaded" and "cached disabled" benchmarks use these settings:

  • Cache disabled: Disable the cache by setting the environment variable GOJEKYLL_DISABLE_CACHE=1.
  • Single-threaded: Disable threading by setting GOMAXPROCS=1.

For example:

GOMAXPROCS=1 GOJEKYLL_DISABLE_CACHE=1 hyperfine --warmup 2 "gojekyll build -s ${SITE_SRC}"
GOMAXPROCS=1 hyperfine --warmup 2 "gojekyll build -s ${SITE_SRC}"
GOJEKYLL_DISABLE_CACHE=1 hyperfine --warmup 2 "gojekyll build -s ${SITE_SRC}"
hyperfine --warmup 2 "gojekyll build -s ${SITE_SRC}"

If you run into an error after a few runs, add the --show-ouput option to hyperfine.

Coverage

./scripts/coverage && go tool cover -html=coverage.out

Profiling

gojekyll -s path/to/site benchmark
go tool pprof --web gojekyll gojekyll.prof